I have observed since about January of this year that, when trying to get PDF images, there are spurious faults (restFaults, not restErrors) received from OPS. The fault code and message reads:
SERVER.DomainAccess The request could not be processed. Please try again later.
I post below a few example queries from yesterday which produced this fault:
https://ops.epo.org/3.2/rest-services/p ... /fullimage
https://ops.epo.org/3.2/rest-services/p ... .A1/images
https://ops.epo.org/3.2/rest-services/p ... .A1/images
https://ops.epo.org/3.2/rest-services/p ... .A1/images
https://ops.epo.org/3.2/rest-services/p ... /fullimage
https://ops.epo.org/3.2/rest-services/p ... .A2/images
https://ops.epo.org/3.2/rest-services/p ... .A1/images
When trying the above queries today no faults were received at all. So it seems not a problem in the queries but a new behaviour implemented in the OPS servers. What is this new behaviour, is it some new feature of Fair Usage Policy?
mike_k43
Internal Server Faults when trying to get PDF images
-
- Posts: 1298
- Joined: Thu Feb 22, 2007 5:32 pm
Re: Internal Server Faults when trying to get PDF images
Hi,
Its a bit hard now to judge why you could not get image data before but now you do. We didn't change anything in PDF's and even if it would it would not be reflected in fair use.
Just one question are you saying you get entire full image without having page by page requests (Range=1) in URL?
What is your Throttling URL say now as oppose to before? Because we had very heavy traffic since January due to the new subscription cycle so it could be that this was causing some issues with data loading if the system was in overall "buy" status in Throttling?
Regards,
Vesna for OPS
Its a bit hard now to judge why you could not get image data before but now you do. We didn't change anything in PDF's and even if it would it would not be reflected in fair use.
Just one question are you saying you get entire full image without having page by page requests (Range=1) in URL?
What is your Throttling URL say now as oppose to before? Because we had very heavy traffic since January due to the new subscription cycle so it could be that this was causing some issues with data loading if the system was in overall "buy" status in Throttling?
Regards,
Vesna for OPS