opengeospatial / ets-csw202

Executable Test Suite for CSW 2.0.2
Other
2 stars 1 forks source link

csw-2.0.2-GetRecordById-tc6.1 - firewall will not allow unsupported OutputSchema response #35

Closed sptillma closed 4 years ago

sptillma commented 4 years ago

CSW test csw-2.0.2-GetRecordById-tc6.1 sends the following request including a bogus OutputSchema value. http://ogc.intergraph.com/erdas-apollo/catalog/wrs/WRS?OutputSchema=http://example.org/unsupported&Version=2.0.2...

However, our test site is still controlled by our firewall and will not allow that communication. If we change it to a machine that we can reach like: http://ogc.intergraph.com/erdas-apollo/catalog/wrs/WRS?OutputSchema=http://ogc.intergraph.com/unsupported&Version=2.0.2&Request=GetRecordById&Service=CSW&Id=urn:uuid:19887a8a-f6b0-4a63-ae56-7fba0e17801f

...We return the following exception which is what is expected (you can try the above link):

(Error.InvalidOutputSchema)OutputSchema is invalid.
dstenger commented 4 years ago

Thank you for reporting. So, test csw-2.0.2-GetRecordById-tc6.1 is failing when using second request? What are the input parameters when starting a test run?

sptillma commented 4 years ago

I don’t really see this as a problem with the CITE tests, but rather I see it as a test that will create problems for people with strict firewalls. So I am really only filing this as a means to get a waiver on this test. I will try to explain it below, but I don’t expect there is anything to change in the test itself.

CSW 2.0.2 csw-2.0.2-GetRecordById-tc6.1 Test Name: csw-2.0.2-GetRecordById-tc6.1 Test Description: The response to a GetRecordById request with an unsupported OutputSchema parameter value must include an exception report. Test Result: FAILED Test Requests 1: Method: GET URL: http://ogc.intergraph.com/erdas-apollo/catalog/wrs/WRS?OutputSchema=http://example.org/unsupported&Version=2.0.2&Request=GetRecordById&Service=CSW&Id=urn:uuid:19887a8a-f6b0-4a63-ae56-7fba0e17801f Outputs: ?http://cite.opengeospatial.org/teamengine/reports/Hexagon/s0014/result/csw-2.0.2-GetRecordById-tc6.15252525252.html 1

Reason of Failure:

Error in call to extension function {public org.w3c.dom.NodeList com.occamlab.te.TECore.request(org.w3c.dom.Document,java.lang.String) throws java.lang.Throwable}: Exception in extension function java.lang.reflect.InvocationTargetException

The issue with this request revolves around the address of the output schema. Our firewall will not allow us to access this point. If we change the address to a machine that we can reach inside our firewall but keep it pointing to a non-existent path, we return the following exception which is what is expected (you can try the above link and the one below to see the different responses):

http://ogc.intergraph.com/erdas-apollo/catalog/wrs/WRS?OutputSchema=http://ogc.intergraph.com/unsupported&Version=2.0.2&Request=GetRecordById&Service=CSW&Id=urn:uuid:19887a8a-f6b0-4a63-ae56-7fba0e17801f

We return the following exception which is what is expected (you can try the above link):

(Error.InvalidOutputSchema)OutputSchema is invalid. Regards, Stan From: dstenger Sent: Friday, October 18, 2019 2:36 AM To: opengeospatial/ets-csw202 Cc: TILLMAN Stanley P (Stan) ; Author Subject: Re: [opengeospatial/ets-csw202] csw-2.0.2-GetRecordById-tc6.1 - firewall will not allow unsupported OutputSchema response (#35) This email is not from Hexagon’s Office 365 instance. Please be careful while clicking links, opening attachments, or replying to this email. Thank you for reporting. So, test csw-2.0.2-GetRecordById-tc6.1 is failing when using second request? What are the input parameters when starting a test run? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
dstenger commented 4 years ago

@keshav-nangare Can you please take a look at this issue?

bermud commented 4 years ago

The service seems ok. I suggest next time that the tester also opens the URL to where the schema resides.