Page 1 of 1

"Content-Type: text/plain" for POST in ver. 3.2

Posted: Mon Nov 27, 2017 10:36 am
by EPO / OPS Support
Dear OPS users,

We would like to bring to your attention that since the last release of OPS Ver. 3.2, the POST method has a strict regulation on the value of the Content-Type HTTP request header. Please make sure that the header is set to "Content-Type: text/plain", as any other string will lead to an error code 400 “bad request”.

We are aware that previous versions or releases of OPS were more flexible (see OPS Guide page 9), however this change was introduced in order to be more in line with W3C protocols and decrease the number of invalid requests reaching our back-end systems.

Concerning the POST requests for the authentication token (, the behaviour of the Content-Type request header remains unchanged and as documented (“Content-Type: application/x-www-form-urlencoded”), see also OPS Guide page 34.

OPS support

Re: "Content-Type: text/plain" for POST in ver. 3.2

Posted: Thu Jan 11, 2018 11:11 am
by rharrison1971
Please note the documentation is wrong !!! ... 3.5_en.pdf

Page 9 says
Content-Type: plain/text

and it is imperative for 3.2 that the content type is

Content-Type: text/plain

If this is not set correctly you will get the following error message :

<fault xmlns="">
<message>An unknown error occurred. Please contact Open Patent Services Team ( ... )</message>


Re: "Content-Type: text/plain" for POST in ver. 3.2

Posted: Thu Jan 11, 2018 1:47 pm
by EPO / OPS Support

Yes, you are correct, thank you, will we fix it asap

OPS support