From fa7f75dbfa668f7c473f4d3029354f47d0329894 Mon Sep 17 00:00:00 2001 From: pack Date: Mon, 1 Jun 2026 07:12:29 +0000 Subject: add issues and screenshots --- issues/new_issue_(severity_p3)_03.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 issues/new_issue_(severity_p3)_03.md (limited to 'issues/new_issue_(severity_p3)_03.md') diff --git a/issues/new_issue_(severity_p3)_03.md b/issues/new_issue_(severity_p3)_03.md new file mode 100644 index 0000000..f318953 --- /dev/null +++ b/issues/new_issue_(severity_p3)_03.md @@ -0,0 +1,31 @@ +[Edge-Case] [P3] Non-standard/unhandled HTTP status codes render raw error pages +without user-friendly messaging + +**Severity:** P3 (Low) + +**Issue Type:** Edge Case + +**Frequency:** Everytime + +**Environment:** +- Browser: Firefox 128 / Linux (Artix) +- OS: Artix Linux, x86_64 +- URL: https://the-internet.herokuapp.com/status_codes + +**Steps to Reproduce:** +1. Navigate to https://the-internet.herokuapp.com/status_codes +2. Click the "404" link — observe raw "Not Found" error text +3. Click the "500" link — observe raw "Internal Server Error" text +4. Manually navigate to /status_codes/1000 — observe unhandled response + +**Expected:** Error pages should display user-friendly messages with navigation +options (e.g. "Page not found. Return to homepage."). Non-standard codes should +be caught and handled gracefully. + +**Actual:** All error status codes (404, 500, and non-standard codes like 1000) +render server error text with "Heroku" branding, yet no navigation links, and +no guidance for the user to recover. Non-standard codes are not caught by any +fallback handler. + +**Severity:** P3 — No data loss, but poor user experience. Users encountering +errors have no path back into the application. -- cgit v1.2.3