Closed Bug 652627 Opened 13 years ago Closed 13 years ago

Internal Server Error - 500 error

Categories

(Websites Graveyard :: markup.mozilla.org, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mbrandt, Assigned: brez)

References

()

Details

(Whiteboard: [stage])

Attachments

(1 file)

Attached image 500 error
Steps to reproduce:
1. go to https://markup.allizom.org/en/a

[13:18:23.379] GET https://markup.allizom.org/en/a [HTTP/1.1 500 Internal Server Error 173ms]
Depends on: 652630
My crystal ball predicts, this happens because there is no 404 error template nor a 500 one, so the app gives up and explodes.
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: --- → 1.0
Severity: normal → blocker
Assignee: nobody → jbresnik
Priority: -- → P1
Is this really a BLOCKER ?
Sorry, accidentally put in the wrong value. This should be resolved for 1.0 regardless.
Severity: blocker → major
I feel this is actually critical ("this" being the broader issue from duped bug 652241 about the Django setup not handling bad/malformed URLs and exceptions), since allowing proper stack traces from the Django side to be sent to the team would help us better-triage HTTP 500 errors.  Setting as such.
Severity: major → critical
This is caused believe it or not because the server is *not in DEBUG mode and it can't find a 404.html template (resulting in a 500 error, template not found) i.e. it's *not the app throwing a 500 error for bad URLs (in dev, with DEBUG on, you can see the debug 404 page -- it's returning 404s properly for bad urls - I added some very simple templates for 404 and 500 but we need a designer to make them legit.  Closing because it just needs a designer and should be a new ticket
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
(In reply to comment #6)
> This is caused believe it or not because the server is *not in DEBUG mode and
> it can't find a 404.html template (resulting in a 500 error, template not
> found) i.e. it's *not the app throwing a 500 error for bad URLs (in dev, with
> DEBUG on, you can see the debug 404 page -- it's returning 404s properly for
> bad urls - I added some very simple templates for 404 and 500 but we need a
> designer to make them legit.  Closing because it just needs a designer and
> should be a new ticket

I spun off bug 653864 about this.
QA verified. A templated 404 error page is displayed.
Status: RESOLVED → VERIFIED
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: