-
Improvement
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
We currently serve API requests from /[uuid]/low-level and /api/v1/[uuid]/low-level.
In order to make other things easier, such as caching and rate limiting, it would be best to serve all API requests from a common prefix. So we should change the legacy GET api views to redirect to the /api/v1 views with HTTP 301.
We should leave the POST endpoint as-is, because the submission client still submits to this one.
Redirect old legacy API endpoints to new endpoint with http redirect
-
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
We currently serve API requests from /[uuid]/low-level and /api/v1/[uuid]/low-level.
In order to make other things easier, such as caching and rate limiting, it would be best to serve all API requests from a common prefix. So we should change the legacy GET api views to redirect to the /api/v1 views with HTTP 301.
We should leave the POST endpoint as-is, because the submission client still submits to this one.
-
Rohan Pillai
-
- Votes:
-
0 Vote for this issue
- Watchers:
-
1 Start watching this issue
- Created:
- Updated:
| Version | Package |
|---|