Closed Bug 749066 Opened 13 years ago Closed 13 years ago

Setting up pre-auth from the detail page of an app results in a 403

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect, P2)

Product:
addons.mozilla.org Graveyard
Component:
Public Pages
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: krupa.mozbugs, Assigned: cvan)

References

Details

(Whiteboard: regression)

steps to reproduce: 1. Pick an app which has purchase refunded 2. From its detail page, try to set up preauth actual behavior: preauth returns a 403. [20:40:00.170] POST https://marketplace-dev.allizom.org/en-US/app/fefsagsea/purchase/preapproval [HTTP/1.1 403 FORBIDDEN 49ms] screencast: http://www.screencast.com/t/V9Cz3AeTGY
This happens with a lot of apps since CSRF verification is failing. Cvan is fixing it.
Priority: P4 → P2
Summary: Setting up preauth from the details page of a refunded app results in a 403 → Setting up preauth from the details page of an app results in a 403
https://github.com/mozilla/zamboni/commit/168ab14
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee: nobody → cvan
Target Milestone: --- → 6.5.2
Whiteboard: [edgecase]
Whiteboard: regression
Summary: Setting up preauth from the details page of an app results in a 403 → Setting up pre-auth from the detail page of an app results in a 403
Fixed by design. Pre-auth not available anymore from detail page.
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.