If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Send no-cache headers when the user is not anonymous

RESOLVED WONTFIX

Status

Product:
addons.mozilla.org Graveyard
Component:
Public Pages
RESOLVED WONTFIX
Reported:
7 years ago
Modified:
2 years ago

People

(Reporter: jbalogh, Unassigned)

Tracking

Target:
Q4 2011

Details
(Reporter)

Description

•
7 years ago 
Right now we depend on zeus to do this by looking at cookies, but setting the no-cache header gives us stronger privacy control.
Target Milestone: 5.12.3 → 4.x (triaged)

Comment 1

•
7 years ago 
When we do this, let's not overwrite cache-control if it's already there (eg. the statistics csvs/json).

Updated

•
7 years ago
Blocks: 613349
Whiteboard: [reopen blocked bug when fixed]
 (Reporter)

Comment 2

•
6 years ago 
We need to manage our own HTTP caching once apps start requiring login.
Target Milestone: 4.x (triaged) → Q4 2011
 (Reporter)

Updated

•
6 years ago
Assignee: jbalogh → nobody

Comment 3

•
6 years ago 
We turned off HTTP caching.  Not reopening blocked bug because that's how the rules currently work.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
Whiteboard: [reopen blocked bug when fixed]
 (Assignee)

Updated

•
2 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.