Closed
Bug 656128
Opened 13 years ago
Closed 13 years ago
500/Internal Server Error with manipulated /linear/ trailing path
Categories
(Websites Graveyard :: markup.mozilla.org, defect, P1)
Websites Graveyard
markup.mozilla.org
Tracking
(Not tracked)
VERIFIED
FIXED
1.1
People
(Reporter: stephend, Assigned: adam)
References
()
Details
Attachments
(1 file)
580.00 KB,
image/png
|
Details |
https://markup-dev.allizom.org/en-US/#/linear/8CK9x gives me a 500 Internal Server Error (but I don't yet have a Django stack).
Assignee | ||
Comment 1•13 years ago
|
||
Not of major importance, IMO, but this case could be handled better. I'll work on it.
Assignee: nobody → adam
Reporter | ||
Comment 2•13 years ago
|
||
If you can hold off fixing this until we've investigated why we're not getting Django tracebacks emailed to us when we hit this exception, that'd be appreciated (bug 656345).
Depends on: 656345
Comment 3•13 years ago
|
||
(In reply to comment #0) What are the repro steps, so I can reproduce in my local environment?
Reporter | ||
Comment 4•13 years ago
|
||
(In reply to comment #3) > (In reply to comment #0) > What are the repro steps, so I can reproduce in my local environment? Wouldn't it just be running against your local instance, with path: /en-US/#/linear/8CK9x, or something similar?
Comment 5•13 years ago
|
||
Works for me. Perhaps there is data or conditions that trigger the error?
Updated•13 years ago
|
Priority: -- → P1
Was looking into this to recreate 656345 and discovered that it's really a 404 error - when a mark is not found it returns a HttpResponseServerError (500) - should probably return an XHR of 404 and the view would behave accordingly.. ?
Reporter | ||
Comment 7•13 years ago
|
||
(In reply to comment #6) > Was looking into this to recreate 656345 and discovered that it's really a > 404 error - when a mark is not found it returns a HttpResponseServerError > (500) - should probably return an XHR of 404 and the view would behave > accordingly.. ? Seems right to me.
Comment 10•13 years ago
|
||
Half the fix is here https://github.com/mozilla/markup/commit/be406afc42a19885e667f97ba4d7e10047607dc8 Adam will update the view to handle 404s - leaving as open
Assignee | ||
Comment 11•13 years ago
|
||
Adam updated the view to handle 404s - resolving as fixed. https://github.com/mozilla/markup/commit/06188ef483ca75c70bbd94ba3b1b7568641ab9ab
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 12•13 years ago
|
||
Reporter | ||
Comment 13•13 years ago
|
||
Verified FIXED on: [13:34:12.026] GET https://markup-dev.allizom.org/requests/marks_by_reference?reference=8CK9x&include_forward=20&include_back=20&include_mark=1 [HTTP/1.1 404 NOT FOUND 4335ms]
Status: RESOLVED → VERIFIED
Updated•2 years ago
|
Product: Websites → Websites Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•