Closed Bug 1250976 Opened 10 years ago Closed 10 years ago

410 returned from /api/v1/<resource>/ with trailing slash

Categories

(developer.mozilla.org Graveyard :: BrowserCompat, defect)

Product:
developer.mozilla.org Graveyard
Component:
BrowserCompat
Platform:
All
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jwhitlock, Assigned: jwhitlock)

References

Details

(Whiteboard: [type:bug][bc:infra][bc:milestone=bicycle])

What did you do? ================ Go to https://browsercompat.herokuapp.com/api/v1/browsers/ What happened? ============== A "410 Gone" response and an empty page What should have happened? ========================== A 301 permanent redirect to https://browsercompat.herokuapp.com/api/v1/browsers Is there anything else we should know? ====================================== First reported in bug 1229785, but in the context of providing a styled 410 page, which may still be needed.
Assignee: nobody → jwhitlock
Blocks: 1240757
See Also: → 1229785
Whiteboard: [specification][type:bug] → [type:bug][bc:infra][bc:milestone=bicycle]
Commits pushed to master at https://github.com/mdn/browsercompat https://github.com/mdn/browsercompat/commit/5fd9caba30b652532238e4c0019be3dc4df70a64 bug 1250976 - Redirect to slashless API URLs 301 redirect /api/v1/browsers/ to /api/v1/browsers. This worked (with a 302 redirect) before the switch to namespaced v1/v2 API URLs. https://github.com/mdn/browsercompat/commit/0b6aecedb849cf1f482c04c9e200e323d2dbda76 Merge pull request #110 from mdn/redirect_1250976 fix bug 1250976 - Redirect to slashless API URLs
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.