Last modified: 2012-12-21 18:48:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42856, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40856 - Cached UA agent failures cause broken CSS due to Varnish caching
Cached UA agent failures cause broken CSS due to Varnish caching
Status: NEW
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
wmf-deployment
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-08 13:19 UTC by Derk-Jan Hartman
Modified: 2012-12-21 18:48 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
HTTP response headers (12.37 KB, text/plain)
2012-10-08 22:29 UTC, Kevin Israel (PleaseStand)
Details

Description Derk-Jan Hartman 2012-10-08 13:19:05 UTC
There are some reports of users on en:WP:VP/T that they had no diff styling anymore. It was figured out that some users were getting: "Scripts should use an informative User-Agent string with contact information, or they may be IP-blocked without notice." on the below URL, even though they were using FF15 and Google Chrome.

http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=mediawiki.action.history.diff&only=styles&skin=vector&*

I think that this might have been due to squid caching + client side caching of the URL?

Probably failures like that should aggressively make sure that they are not client side cached (Cache-Control: no-cache, must-revalidate instead of public), and have a short squid caching (a minute should be more than plenty to withstand any trouble right ?).
Comment 1 Kevin Israel (PleaseStand) 2012-10-08 22:29:03 UTC
Created attachment 11160 [details]
HTTP response headers

Through some testing with netcat, I can confirm Varnish is caching these errors, apparently despite the "Cache-control: no-cache" header.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links