New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ETS expects unquoted strings while using Accept: application/json
#55
Comments
@jerstlouis I have created a fix for this (see #76). Could you maybe provide a test endpoint, so I can verify my fix? |
@bpross-52n We were testing this with our EchoProcess at https://maps.gnosis.earth/ogcapi/processes/echo If this was preventing the ETS to pass, we might have set up a work-around to pass the compliance test. Right now POSTing to https://maps.gnosis.earth/ogcapi/processes/echo/execution: {
"process" : "https://maps.gnosis.earth/ogcapi/processes/echo",
"inputs" : {
"stringInput" : "Value1"
},
"response": "raw"
} will return the string unquoted whether using If the fix is for the ETS to not use Note that this is somewhat related to #60 (still open) and #61 (fixed?) whereas the number of outputs and the "raw" behavior will change depending on what outputs are to be returned. |
@jerstlouis We fixed it by leaving out the |
@gfenoy I have created a pull request to fix this issue. However, the status document of the finished job returns the following link:
Imho, the relation should be |
I agree. |
Describe the bug
It seems that the ETS expects single value raw text outputs as unquoted strings, however it uses an
Accept:
header withapplication/json
for making this request. This is inconsistent and causes compatibility problems with trying to respect OGC API Web Guidelines 10 - Flexible content negotiation and upcoming version 2.0.Expected behavior
If unquoted text values are expected,
Accept: text/plain
(for text) orapplication/octet-stream
(for binary data) should be used (or at least not including anAccept:
header at all).The text was updated successfully, but these errors were encountered: