Relax requirement to use HTTP 501 #415 (#418)

Open-EO · Oct 22, 2021 · 592e266 · 592e266
1 parent e171f0d
commit 592e266
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -21,6 +21,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 
 - Updated STAC specification examples and references to v1.0.0.
+- Relaxed requirement that unsupported endpoints must return HTTP status code 501. Instead also HTTP status code 404 can be used (and is regularly used in practice). [#415](https://github.com/Open-EO/openeo-api/issues/415)
 
 ### Fixed
 

diff --git a/openapi.yaml b/openapi.yaml
@@ -112,11 +112,15 @@ info:
 
     - **404 Not Found**:
       The resource specified by the path does not exist, i.e. one of the resources belonging to the specified identifiers are not available at the back-end.
-      *Note:* Unsupported endpoints MUST use HTTP status code 501.
+      *Note:* Unsupported endpoints MAY also return HTTP status code 501.
 
     - **500 Internal Server Error**:
       The error has its origin on server side and no other status code in the 500 range is suitable.
 
+    - **501 Not Implemented**:
+      The requested endpoint is specified by the openEO API, but is not implemented (yet) by the back-end.
+      *Note:* Unsupported endpoints MAY also return HTTP status code 404.
+
 
     If a HTTP status code in the 400 range is returned, the client SHOULD NOT repeat the request without modifications. For HTTP status code in the 500 range, the client MAY repeat the same request later.