Page MenuHomePhabricator

Cached UA agent failures cause broken CSS due to Varnish caching
Closed, DeclinedPublic

Description

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 ?).


Version: wmf-deployment
Severity: normal

Details

Reference
bz40856

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:06 AM
bzimport set Reference to bz40856.
bzimport added a subscriber: Unknown Object (MLST).

Created attachment 11160
HTTP response headers

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

Attached:

Krinkle subscribed.

I can no longer reproduce this. As far as I can tell, Varnish does not cache these errors and/or we no longer produce this error in the first place.

Additionally, bits.wikimedia.org has been folded back into the regular mediawiki endpoints. (T107430)