Closed christophfriedrich closed 4 years ago
Thanks for reporting this. I'll check that later.
The 200 OK status code is correct. The status code is about whether the request succeeded, but doesn't imply anything on the validation.
200 + 0 errors in list => process graph valid 200 + 1+ errors in list => process graph invalid 400/500 error => your request was incorrect (e.g. send XML instead of JSON) or server errors (e.g. busy/not found/...)
Did you send only the process graph or was it wrapped into a { process_graph: ... }? Please check the API how a valid request has to be sent.
Re: 200 OK You're too quick! :D See edit above. I noticed that status code because in openEO v0.3 a valid process graph was characterized by a 204. But the change is very reasonable.
Re: Was it wrapped in process_graph
?
Of course it was not, the mistake was on the client side and you found it spot on :upside_down_face:
I just tested the first process graph that is currently shared on the Hub (the max NDVI one, pasted below) against the
/validation
endpoint of the driver.I get this reponse:
~(Interestingly with a
200 OK
status code; I'll open a separate issue for that.)~ Edit: I re-read the spec and apparently that is absolutely correct behaviour.But when I paste that same process graph into the Web Editor, save it as a Web Service and show that service on the map, everything works perfectly fine.
Process graph used: