Closed Bug 613574 Opened 15 years ago Closed 15 years ago

Need a handler for the Django session cookie - logged-in state not reflected on SAMO

Categories

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

defect

Tracking

(Not tracked)

VERIFIED WORKSFORME
5.12.5

People

(Reporter: stephend, Assigned: jbalogh)

Details

Spun off from bug 600372, the logged-in state is reflected when logging in to prod and loading, say https://addons.mozilla.org/en-US/firefox/discovery/3.7pre/Darwin, but not from SAMO: https://services.addons.mozilla.org/en-US/firefox/discovery/3.7pre/Darwin. Jeff notes that we're sending the sessionid cookie right, but we don't yet have a handler for the django session cookie.
Not sure what this means
Priority: -- → P3
Target Milestone: --- → 5.12.5
Our AuthenticationBackends look for the AMOv3 cookie to propagate remora sessions. But there's no AMOv3 cookie on samo since the cookie domain is not correct, so only the Django sessionid cookie is available. We have nothing to pick up sessionid so we treat the user as anonymous.
Assignee: nobody → jbalogh
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
I see the same as you, Jeff; dunno what happened, but hey; fixed. Verified WFM.
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.