search

opengeospatial / ets-ogcapi-processes10

Other
3 stars 3 forks source link

status code error owing to unsupported async #10

Closed pcdion closed 2 years ago

pcdion commented 2 years ago

The jobControlOptions of our the echo process do not list async capability and 200 is a valid status code if the server supports sync. However, the ogcapi-processes-1.0 test returns an error with "Got unexpected status code: 200" as the reason given for several tests.

e.g. test Job Creation Success Async

dstenger commented 2 years ago

Thank you for reporting. We will do further investigation. Is there a test service available we can use to reproduce the behavior?

jerstlouis commented 2 years ago

@dstenger not at the moment, sorry. This experimental version of our GNOSIS Map Server has not yet been integrated into our deployed software.

bpross-52n commented 2 years ago

We discussed this last Monday in the OGC API - Processes SWG. It is correct, that a HTTP status code 200 is a valid response if the server supports synchronous execution. I will update the ets.