Closed
Bug 833678
Opened 11 years ago
Closed 11 years ago
CSRF failure doing app purchase
Categories
(Marketplace Graveyard :: Consumer Pages, defect, P2)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 864663
People
(Reporter: krupa.mozbugs, Unassigned)
References
Details
Attachments
(1 file)
59.83 KB,
image/png
|
Details |
steps to reproduce: 0. Tester is logged into marketplace-dev 5 hours earlier 1. Click on the purchase button for 'private yacht' reproducible? sometimes expected behavior: - CSRF failures are dealt with gracefully. - If the user session has expired, we make them log in again after clicking purchase. observed behavior: CSRF failure showing an ugly 403 error to the user. See screenshot.
Comment 1•11 years ago
|
||
I've seen this too. This might be related to memcache going away temporarily.
Comment 2•11 years ago
|
||
(In reply to Kumar McMillan [:kumar] from comment #1) > I've seen this too. This might be related to memcache going away temporarily. you mean something on -dev or does memcache go away other times?
Comment 3•11 years ago
|
||
I've only seen it on dev so I'm not sure. It's worth a try to turn off memcache (to simulate an outage) to see how much of the payment flow still works.
Comment 4•11 years ago
|
||
I rarely see this, marking as P3. Seems like something we should address though.
Priority: -- → P3
Reporter | ||
Comment 5•11 years ago
|
||
I have seen this twice in the last week. So, moving it to P2.
Priority: P3 → P2
Comment 6•11 years ago
|
||
pretty sure this is the same as bug 864663
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•