Closed greatzzk closed 11 months ago
Hi @greatzzk, we noticed that the server responds a HTTP 404 error with no body, if we execute the request in your comment above. Could you have a look into that?
@bpross-52n i am not sure if i understand your comment. isn't the response displaying in screenshot above showing it is inside "body" of the response?
@greatzzk You are right, sorry. I only opened the URL in the browser and there no body was shown, only a browser error page. With more advanced tools the body is shown. Sorry for the confusion.
@greatzzk The problem is that the test suite is only looking for Envelope-Elements in the CoverageDescription and your service has EnvelopWithTimePeriod, which is fine, of course. So I think this is a bug in the test suite. I will work on a solution.
My current findings are:
The failing test (see the code here) sends the following request:
http://54.90.187.123:6080/arcgis/services/mynetcdf/ImageServer/WCSServer?service=WCS&VERSION=2.0.1&request=GetCoverage&coverageid=mynetcdf&subset=x(-1.67048810872E7)&subset=x(-1.67048810872E7,-1.67048810872E7)
Response:
<ows:ExceptionReport
xmlns:ows="http://www.opengis.net/ows/2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.0.0"
xsi:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd">
<ows:Exception exceptionCode="InvalidSubsetting"
locator="(-1.67048810872E7,-1.67048810872E7)" />
</ows:ExceptionReport>
Other services return an InvalidAxisLabel exception code here, because of the duplicate x-axis, thus pasing the test. We will confirm that this is the correct behavior.
Requirement 41 is specified in this document https://portal.opengeospatial.org/files/?artifact_id=48428. @bpross-52n Can you please check whether InvalidAxisLabel and InvalidSubsetting are correct in this case and adjust the test accordingly?
The test was modified now so that a valid subsetting request is created (first axis with correct values, second axis with correct values) and then a duplicate of the first axis with correct values is appended to the request. This leads now to the expexted exception code InvalidAxisLabel. An InvalidSubsetting exception should not be returned anymore, because the subsetting is correct. I tested with the service referenced here.
i verified this issue on te2 against my server. cheers!!
error msg from test:
but i think my server has the correct response containing an "invalidAxisLabel" exception. http://54.90.187.123:6080/arcgis/services/mynetcdf/ImageServer/WCSServer?&request=GetCoverage&coverageid=mynetcdf&service=WCS&VERSION=2.0.1&subset=fakeaxislabel(10)
could you help investigate?