You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I make a request to an endpoint for a collection that doesn't exists, I get a 404
In [14]: importrequestsIn [19]: r=requests.get("https://pct-pqe-staging.westeurope.cloudapp.azure.com/stac/v1/collections/not-a-collection")
In [20]: r.status_codeOut[20]: 404
But if I make a request to that collection's /items I get a 200, and the response includes an empty FeatureCollection.
I also can't find anything in the spec, but this smells funny to me. I think it would be more RESTful to return a 404 in this case since the resource being requested doesn't exist on the server (an item can't exist outside of a collection).
OAFeat Part 1 says for both /collection/ and /collection//items:
If the parameter collectionId does not exist on the server, the status code of the response
will be 404 (see [Table 2](https://docs.opengeospatial.org/is/17-069r3/17-069r3.html#status_codes)).
If I make a request to an endpoint for a collection that doesn't exists, I get a 404
But if I make a request to that collection's
/items
I get a 200, and the response includes an empty FeatureCollection.I wanted to verify that this is the expected behavior. I didn't find anything in the API spec, but I admittedly didn't look too closely.
Reported in TomAugspurger/stac-dask-discussion#1
The text was updated successfully, but these errors were encountered: