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
With the addition of the human-readable landing page, the redirect middleware was changed to avoid infinite loops on the base URLs.
This also means that single-entry endpoints are no longer redirected from /endpoint/id/ to /endpoint/id.
The text was updated successfully, but these errors were encountered:
I don't think this is an issue (https://optimade.herokuapp.com/optimade/v0/structures/mpf_1/ redirects fine for me); the problem was that the slashed endpoints e.g. /structures/ had a defined response (i.e. query structure endpoint with a blank ID) but in this case the matching response is still just return the single entry endpoint.
Do you have a counterexample where it doesn't work?
It must be a thing of heroku then, starting the server locally and going to http://localhost:5000/optimade/v0/structures/mpf_1/ renders the implementation in a state where it tries to find id mpf_1/ (I believe) so it doesn't work - but maybe that is actually the desired result? Since / should be allowed in the id, right?
Closing this, as per my last comment, it is not desired to have the final / (forward slash) removed for single-entry endpoints, as the slash may be part of the id.
With the addition of the human-readable landing page, the redirect middleware was changed to avoid infinite loops on the base URLs.
This also means that single-entry endpoints are no longer redirected from
/endpoint/id/
to/endpoint/id
.The text was updated successfully, but these errors were encountered: