400 BAD request HTTP error code using POST

This space is made available to users of Open Patent Services (OPS) web-service and now also to users of EPO’s bulk data subscription products such as 14. EPO worldwide bibliographic database (DOCDB), 14.11 EPO worldwide legal status database (INPADOC), 14.12 EP full text data, 14.1 EP bibliographic data (EBD)and more.

Users can ask each other questions, exchange experiences and solutions, post ideas. The moderator will use this space to announce changes or other relevant information.
Post Reply

thomasst
Posts: 21
Joined: Thu Sep 25, 2008 10:50 am
Location: Munich
Contact:

400 BAD request HTTP error code using POST

Post by thomasst » Wed Nov 08, 2017 11:46 am

Dear OPS Team,
since the last update of the OPS service 3.2 we receive in our application as a response the error code:
400 BAD request
Our application uses POST requests like
http://ops.epo.org/3.2/rest-services/fa ... tion/docdb
with the POST content like:
US.2003084988.A1
We have analysed the problem and found that there was a chnage in the OPS 3.2 service so that for POST requests no other "Content-Type" header is anymore supported as the "Content-Type: text/plain". All the years before we used in our application for the Content-Type header the string "application/x-www-form-urlencoded" which still works in the OPS 3.1 service.

For the Authentification (token) request however
https://ops.epo.org/3.2/auth/accesstoken
it works only using the header
Content-Type: application/x-www-form-urlencoded in the POST request as writen in your documentation.
For other services in the OPS documentation there is writen that the POST service has no strict regulation concerning the Content-Type header as many application enter this automatically.
If you let this as it is at the moment, you should inform the users of the OPS service of this change and update also the documentation.

Is there a chance, that in the current OPS 3.2 service the Content-Type: application/x-www-form-urlencoded can be used additionally using the services beside the "accesstoken" service again as it was before?

Otherwise we have to update all our software which is used by many clients.

Many thanks
Thomas Stiefvater


EPO / OPS Support
Posts: 999
Joined: Thu Feb 22, 2007 5:32 pm

Re: 400 BAD request HTTP error code using POST - "Content-Type: "

Post by EPO / OPS Support » Wed Nov 08, 2017 1:20 pm

Hi,

Unfortunately, this is not something that we knew or have requested to be done, so we only find out about it from another user of this forum yesterday (see below post). We have asked the developers to synchronise this back as it was in the version before the release but it would take another release to fix that.

We are sorry for inconvenience caused and we are hoping that users with similar issues do read OPS forum treads like yours to avoid having same issues.

Regards,
OPS support


EPO / OPS Support
Posts: 999
Joined: Thu Feb 22, 2007 5:32 pm

Re: 400 BAD request HTTP error code using POST

Post by EPO / OPS Support » Mon Nov 27, 2017 10:38 am

Please see new OPS Announcement:
https://forums.epo.org/content-type-tex ... n-ver-7315

OPS support


Post Reply