To hide banners across domains after a user clicks on a banner's close button, we call Special:HideBanners a lot... As long as this mechanism persists (see T117433 for an investigation of alternatives) it's important that we ensure it works as efficiently as possible. Double-check the Varnish configuration, HTTP headers, PHP and JS code, and anything else that could be tuned to reduce the load all around.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Spike | BBlack | T117435 Spike: CentralNotice: Verify that our Special:HideBanners cookie storm works as efficiently as possible | ||
| Open | Spike | None | T256447 Special:HideBanners is not really cacheable |
Event Timeline
Comment Actions
Here are the cache headers we set from the special page:
Cache-Control: public, s-maxage=86400, max-age=0
We arrived at that in a pretty amateur way, and it looks a bit funny in hindsight, so review would be appreciated. The idea is that the response is cacheable by our Varnishes or any intermediate proxy. I don't know why we're preventing client-side caching with max-age=0, but I don't think there's much of a use case for caching on the client though, cos it's rare that any individual will be hitting the same category of close box more than once per year.
Comment Actions
Resolving for now, no movement since last update in 2015. Make a new modern ticket if there's still issues here!