This only affects certain document IDs, with most documents unaffected. However, it is unexpected because the same endpoints work perfectly on version 3.1 (end-of-life) for exactly the same document IDs.
Here are some examples:
https://ops.epo.org/end-of-life/rest-se ... nts/images
https://ops.epo.org/end-of-life/rest-se ... nts/images
https://ops.epo.org/end-of-life/rest-se ... nts/images
https://ops.epo.org/end-of-life/rest-se ... nts/images
https://ops.epo.org/end-of-life/rest-se ... nts/images
https://ops.epo.org/end-of-life/rest-se ... nts/images
https://ops.epo.org/end-of-life/rest-se ... nts/images
The above links work fine. However, when these endpoints are accessed via version 3.2 (with authentication) instead of 'end-of-life', a 404 response is received with the following xml.
Code: Select all
<fault xmlns="http://ops.epo.org">
<code>CLIENT.DomainAccess</code>
<message>An invalid reference was used in request. Please check if the reference is valid for this service.</message>
</fault>