Closed
Bug 578956
Opened 14 years ago
Closed 14 years ago
Beta Feedback form throws an error (CSRF verification failed. Request aborted.)
Categories
(Input :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: tr, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:2.0b1) Gecko/20100630 Firefox/4.0b1 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:2.0b1) Gecko/20100630 Firefox/4.0b1 ( .NET CLR 3.5.30729) When using the Feedback page accessible from the Feedback dropdown I get a 403 error in response to my feedback. Reproducible: Always Steps to Reproduce: 1. Click on Feedback dropdown to the right of the search box 2. Click on "Firefox made me happy because" or "Firefox made me sad because" 3. Enter any text into the feedback box 4. Click "Submit Feedback" Actual Results: A page that reads thus: Forbidden (403) CSRF verification failed. Request aborted. More information is available with DEBUG=True. Expected Results: Some kind of confirmation of feedback page. I've put this as 'Major' as, if it affects a significant amount of beta users, it would completely ruin the whole point of feedback.
Reporter | ||
Comment 1•14 years ago
|
||
To be sure that it wasn't anything to do with a plugin conflict I disabled all but the official Firefox plugins (so everything apart from Firefox Sync, German dictionary and the Feedback plugin itself). The same results were produced with 3rd party plugins disabled I then disabled Firefox Sync and the German Dictionary leaving Feedback as the only plugin running on the system. Again. I got the same results.
Reporter | ||
Comment 2•14 years ago
|
||
I attempted to use safe mode in case there were other browser settings that were affecting the feedback plugin. My intention was to enter safe mode, switch on the feedback plugin and then attempt to provide feedback. However the add-ons manager appears to think that the feedback plugin is running (as it only provides 'disable' as an option) but the feedback dropdown is not evident to the right of the search box. This may constitute another error. From what I've read about CSRF errors it would appear that the most likely scenario is an error in the verification script which is being picked up as an attempted Fraud but I wanted to make sure I'd thoroughly checked that it wasn't caused by any conflict with plugins etc. Just to be on the safe side.
Comment 3•14 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:2.0b1) Gecko/20100630 BetterPrivacy-1.47 Firefox/4.0b1 Linux la 2.6.26-2-686 #1 SMP Mon Jun 21 05:58:44 UTC 2010 i686 GNU/Linux Debian Lenny I have an identical problem. I have tried disabling add-ons, as above. Also, it is always repeatable.
Updated•14 years ago
|
Component: General → Input
Product: Firefox → Webtools
QA Contact: general → input
Summary: Beta Feedback form throws an error → Beta Feedback form throws an error (CSRF verification failed. Request aborted.)
Version: unspecified → other
Comment 5•14 years ago
|
||
We haven't seen any of this popping up again. If it does, please reopen. Since the CSRF check is based on a cookie, perhaps your cookie settings are preventing it from working properly?
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
1. Feedback failed again. 2. I disabled Yahoo! Mail Notifier and restarted. 3. Feedback worked for the first time ever.
Comment 7•14 years ago
|
||
> We haven't seen any of this popping up again. If it does, please reopen. Also reported in bug 594256, bug 611619, the latest one is recent.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WORKSFORME → ---
Comment 8•14 years ago
|
||
Bug 594256 seemed transient, and bug 611619 was a setting issue on the client side. I don't currently see that there's a bug in the app we would need to fix. Please let me know if you disagree.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•13 years ago
|
Component: Input → General
Product: Webtools → Input
You need to log in
before you can comment on or make changes to this bug.
Description
•