Closed
Bug 436994
Opened 17 years ago
Closed 16 years ago
CSRF error message should return HTTP code 400, not 200
Categories
(addons.mozilla.org Graveyard :: Admin/Editor Tools, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
5.0.5
People
(Reporter: clouserw, Assigned: wenzel)
Details
Attachments
(2 files)
|
572 bytes,
patch
|
clouserw
:
review+
|
Details | Diff | Splinter Review |
|
197.64 KB,
image/png
|
Details |
From bug 435450, the feature list javascript should check the return response from the server. To reproduce:
1) Go to the editor's feature list and add a feature
2) Tamper with the POST request and make the sessioncheck variable invalid
Expected results:
1) A 400 response from the server and an appropriate error
Actual results:
1) A 200 response from the server and it's added to the list. However, it's only added client side and refreshing the page doesn't show the add-on in the list.
| Assignee | ||
Comment 1•17 years ago
|
||
I think the "sessionCheck check" does not set the HTTP response code correctly when receiving an incorrect sessioncheck ID. When I wrote the code, I tried putting incorrect values into the form and when the "add feature" code returns an error, the AJAX javascript honors this correctly, so I am quite sure the CSRF check is at fault here.
| Assignee | ||
Updated•17 years ago
|
Summary: Feature list shouldn't add with bad sessioncheck → CSRF error message should return HTTP code 400, not 200
| Assignee | ||
Comment 2•16 years ago
|
||
Just closing out a few old bugs and this one is a one-liner.
| Assignee | ||
Updated•16 years ago
|
Target Milestone: --- → 5.0.5
| Reporter | ||
Updated•16 years ago
|
Attachment #372027 -
Flags: review?(clouserw) → review+
Comment 4•16 years ago
|
||
Comment 5•16 years ago
|
||
As the screenshot in comment 4 shows, I get a status code/error of 400 returned.
Verified FIXED
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Keywords: push-needed
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•