We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In some cases, the http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd schema is used for the exception. However, the specification states that following schema shall be used: http://schemas.opengis.net/wms/1.3.0/exceptions_1_3_0.xsd
Also see chapter E.2 Service Exception schema of specification (OGC® 06-042).
E.2 Service Exception schema
Following example requests return the wrong exception:
Following example request returns the correct exception:
The text was updated successfully, but these errors were encountered:
https://inspire.brandenburg.de/services/ef_sem_wms?REQUEST=zzzz&SERVICE=WMS is a tricky request because deegree does not know what WMS version is requested. Here, it is not 100% clear what exception shall be returned.
Sorry, something went wrong.
#7678 (deegree#1182) - fixed expection type, improved exception messa…
0aa5efb
…ges, avoid npe
Successfully merging a pull request may close this issue.
In some cases, the http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd schema is used for the exception. However, the specification states that following schema shall be used: http://schemas.opengis.net/wms/1.3.0/exceptions_1_3_0.xsd
Also see chapter
E.2 Service Exception schema
of specification (OGC® 06-042).Following example requests return the wrong exception:
Following example request returns the correct exception:
The text was updated successfully, but these errors were encountered: