Page 1 of 1

Url encoding issue

Posted: Mon Jan 15, 2018 3:55 pm
by allan_ahe
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

Re: Url encoding issue

Posted: Tue Jan 16, 2018 8:09 am
by EPO / OPS Support
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

Re: Url encoding issue

Posted: Tue Jan 16, 2018 8:44 am
by allan_ahe
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

Re: Url encoding issue

Posted: Tue Jan 16, 2018 9:58 am
by EPO / OPS Support
Thanks a lot. I have issue a ticket for developers to fix that.

Regards,
OPS support