Closed Bug 1229785 Opened 10 years ago Closed 8 years ago

No HTTP 410 error page

Categories

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

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

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: mbrandt, Unassigned)

References

Details

(Whiteboard: [bc:infra][bc:front][bc:milestone=car])

Several URLs return a HTTP 410 status and un-styled pages. Is this the appropriate HTTP response? https://browsercompat.herokuapp.com/api/v1/historical_supports/ https://browsercompat.herokuapp.com/api/v1/browsers/ https://browsercompat.herokuapp.com/api/v1/historical_browsers/ Suggested: Is a 410 the correct HTTP response? Return a 4xx error template/HTML to the user. Actual: No HTML is returned.
410 Gone means a resource is no longer available. This should instead 301 redirect to the real URLs, such as https://browsercompat.herokuapp.com/api/v1/browsers/ 410 Gone may be an expected response for deleted content with bug 1159349.
Blocks: 996570
Keywords: in-triage
OS: Unspecified → All
Hardware: Unspecified → All
Summary: [browsercompat] No HTTP 410 error page → No HTTP 410 error page
Whiteboard: [bc:infra][bc:front]
Mentor: jwhitlock
Blocks: 1159349
No longer blocks: 996570
Whiteboard: [bc:infra][bc:front] → [bc:infra][bc:front][bc:milestone=car]
See Also: → 1250976
Mentor: jwhitlock
The BrowserCompat project is canceled. See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.