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
fpagnoux
changed the title
Redirect /parameter/path.to.param to parameter/path/to/param
Redirect /parameter/path.to.param to parameter/path/to/param
Jul 24, 2018
I'll just add that not following redirects in an API is much more common than one would expect, as many server-side request libraries do not do it by default to prevent blocking.
At the moment both forms are working, and it seems to me like this is just fine. We need only three lines of code to try both routes, and redirecting would likely not save any implementation complexity. In sum, I don't see much value in this issue, recommend closing. Any objections?
Depends on #694
The
/parameter/path.to.param
route is deprecated. Use a301
to redirect it to the proper new routeparameter/path/to/param
This is a breaking change, as clients which do not follow redirects may break if using the old path.
The text was updated successfully, but these errors were encountered: