-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OWS Exception Report vs Service Exception Report #654
Comments
Dear @JohannaOtt, We will analyze this issue and we will come back to you with more information. Best regards, |
Just a note: In both instance, the test
Therefore, I guess that the other tests are not performed correctly. |
The problem occurred in a staging instance after making this change which is not in accordance to the reported issue. |
Dear @JohannaOtt, We have reviewed and updated the current staging instance, which had a remaining change for issue #584, as @mpleic mentioned in the comment above. We decided to revert this change. Please, let us know if this change was valid for you. Best regards. |
I can confirm that I do not get an issue any longer for the http-request-getmap-no-width-height test case |
For WMS requests with missing/wrong parameters, there are two kinds of exception reports that can be returned by the service - OWS exception reports and service expection reports.
![grafik](https://user-images.githubusercontent.com/34163838/141314667-59d6ca36-1dea-46bf-adb1-a5a98c446775.png)
This WMS gets a validation error concerning the exception report thrown for missing width/height parameters on the staging instance (production instance is currently not working):
Indeed the service returns a ServiceExceptionReport (no OWS exception report) for the respective request
The issue is that for other requests (for example missing bounding box), the service is also returning a ServiceExceptionReport, but the validator is not complaining in this case:
![grafik](https://user-images.githubusercontent.com/34163838/141315074-b7b4c43f-5e09-4b6e-860b-079f3ea40e5d.png)
I seem to remember that the exception type was changed because the OWS exception report used to cause errors in the validator - now one of the ServiceExceptionReports does not pass.
Is there a rule, for which wrong requests which type of exception report is expected? Why is it not allowed to return a ServiceExceptionReport for missing height/width parameter but is allowed for missing bbox parameter?
The text was updated successfully, but these errors were encountered: