OWS Exception Report vs Service Exception Report

[JohannaOtt]

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.
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:

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?

[arantzaetxebarria]

Dear @JohannaOtt,

We will analyze this issue and we will come back to you with more information.

Best regards,
Arantza

[alitka]

Just a note: In both instance, the test at04-getcapabilities-xml-schema-validation (check-xml-schema-valid) throw an error:

Schema not valid: [org.xml.sax.SAXException: Fatal error: org.xml.sax.SAXParseException; lineNumber: 102; columnNumber: 32; cvc-complex-type.2.4.a: Invalid content was found starting with element 'sld:GetLegendGraphic'. One of '{"http://www.opengis.net/wms":_ExtendedOperation}' is expected. Response did not validate against schema 'http://inspire.ec.europa.eu/schemas/inspire_vs/1.0/inspire_vs.xsd'.]

Therefore, I guess that the other tests are not performed correctly.

[mpleic]

The problem occurred in a staging instance after making this change which is not in accordance to the reported issue.
I analyzed the problem and reported it here as well as the solution proposal.
The change mentioned above is now reversed but it is not deployed. A pull request for it is still open. So after accepting this merge request and deploying staging instace this problem will be solved, but the issue #584 remains unresolved.

[dperezBM]

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.

[JohannaOtt]

I can confirm that I do not get an issue any longer for the http-request-getmap-no-width-height test case

Test report
Test run on 17 02 - 09.12.2021 with test suite Conformance Class View Service WMS.html.zip