Url encoding issue

This space is made available to users of Open Patent Services (OPS) web-service and now also to users of EPO’s raw data subscription products such as 14.7 DOCDB - worldwide bibliographic master database, 14.11 Worldwide legal status (INPADOC), 14.12 EP full text in XML, 14.1 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

allan_ahe
Posts: 2
Joined: Mon Jan 15, 2018 11:15 am

Url encoding issue

Post by allan_ahe » Mon Jan 15, 2018 3:55 pm

Dear support team,

Since today I cannot retrieve all images when url encoding for part "?Range=" is turned on, meaning, for instance :

"http://ops.epo.org/3.2/rest-services/published-data/images/CN/205604227/U/fullimage.tiff%3fRange%3d6" doesn't work anymore (it did some days ago)

but

"http://ops.epo.org/3.2/rest-services/published-data/images/CN/205604227/U/fullimage.tiff?Range=6" now is working (which is not compliant with current documentation)

To be more precise, I use GET method and i get following error message:

http://ops.epo.org/3.2/rest-services/published-data/images/CN/205604227/U/fullimage.tiff%3fRange%3d6: The remote server returned an error: (400) Bad Request.; <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fault xmlns="http://ops.epo.org">
<code>SERVER.InvalidDocumentId</code>
<message>Incorrect image identifier CN/205604227/U/fullimage.tiff?Range=6</message>
</fault>

Thanks for your help


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

Re: Url encoding issue

Post by EPO / OPS Support » Tue Jan 16, 2018 8:09 am

Hi,
.../3.2/rest-services/published-data/images/CN/205604227/U/fullimage.tiff?Range=6
Is correct way top request page 6 of that tiff, but I am not sure where in our documentation is supposed to be stated otherwise? Can you point me that the page in the document where it says that? We didn’t do any changes in the last few days so I am not use how repose has changed, but “=” and “?” should work fine as always.

Regards,
OPS support


allan_ahe
Posts: 2
Joined: Mon Jan 15, 2018 11:15 am

Re: Url encoding issue

Post by allan_ahe » Tue Jan 16, 2018 8:44 am

Hi,

I use current version of OPS reference guide (http://documents.epo.org/projects/babyl ... 3.5_en.pdf) linked here: http://www.epo.org/searching-for-patent ... html#tab-3.

Rules regarding encoding are located at paragraph "Input construction rule 3: encoding" p.13.

It is stated that encoding "?" in %3f is mandatory and for other symbol like "=", encoding is highly recommended.

Thanks for your investigation


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

Re: Url encoding issue

Post by EPO / OPS Support » Tue Jan 16, 2018 9:58 am

Thanks a lot. I have issue a ticket for developers to fix that.

Regards,
OPS support


Post Reply