crim-ca/weaver

Support expected status response on Sync Job Execute

Closed this issue · 1 comments

Describe the bug

Invalid HTTP status code reported from POST execution of a process job in sync.

How to Reproduce

Run OGC test suite, or run a process manually in sync execution mode.

Expected behavior

Sync Job Execute is expected to return 200 OK, as per the specification
https://github.com/opengeospatial/ogcapi-processes/blob/master/openapi/paths/processes-core/pExecution.yaml

In our case, it reports 201 because a Job object is created even though not running in async.

Context

Appropriate codes are returned by sync.
Added a while ago.