Closed
Bug 982618
Opened 10 years ago
Closed 10 years ago
Please enable caching on aus4.mozilla.org
Categories
(Infrastructure & Operations Graveyard :: WebOps: Product Delivery, task)
Infrastructure & Operations Graveyard
WebOps: Product Delivery
x86_64
Linux
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: nmaul)
Details
We enabled caching by Zeus on aus3.mozilla.org recently. We discussed by e-mail, and found no reason why we shouldn't enable it on aus4, too. Let's do it! Note: please don't add any caching to aus4-admin.mozilla.org, just the user-facing side of aus4.mozilla.org
Assignee | ||
Comment 1•10 years ago
|
||
Completed! strip-nocache rule applied to incoming request override-server-cache-control rule applied to outgoing response caching enabled, set to 30s set to send the following cache header to the client: no-store, must-revalidate, post-check=0, pre-check=0, private (probably overkill, but that's what aus3.m.o sent before we implemented caching on it) This was done on the HTTP and HTTPS VIPs for the public interface. Side note: not sure why there is an HTTP VIP at all... there isn't for AUS3.
Assignee: server-ops-webops → nmaul
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 2•10 years ago
|
||
Ben points out that HTTP redirects to HTTPS, but the HTTP really shouldn't be used for anything (the content should always be provided securely).
Updated•8 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•