Bartosz Dziewoński 5d1a67757a Detect mangled etags from RESTBase and retry via MediaWiki API ... Something is causing the 'ETag' headers produced by the "public" RESTBase (queried directly from the client) to be mangled or lost. My theory is that some proxy or browser extension is doing that. When we detect a bad etag when fetching the page contents, discard the result and try querying the "private" RESTBase via the MediaWiki API (similar to what we do on private wikis, except there we talk directly to Parsoid instead of RESTBase). After I463a84de63, that returns the etag as part of the payload rather than HTTP headers, and should pass unharmed through whatever is mangling the data. Also compare and log the two etags. Bug: T233320 Change-Id: I2ef0ca872597566f74b650aea71bf3f15747a6d7		2019-10-16 19:53:43 +02:00
..
ce	Parse relative hrefs on image nodes like on regular links	2019-09-25 00:25:04 +02:00
dm	Merge "Parse relative hrefs on image nodes like on regular links"	2019-10-11 15:22:29 +00:00
init	Merge "Fix Vector wikitext surface padding overrides when using custom browser font-size"	2019-10-11 15:23:17 +00:00
preinit	Detect mangled etags from RESTBase and retry via MediaWiki API	2019-10-16 19:53:43 +02:00
tests	Merge "Parse relative hrefs on image nodes like on regular links"	2019-10-11 15:22:29 +00:00
themes	SaveDialog: Hide options bar when empty	2019-07-16 14:28:25 +01:00
ui	Merge "Parse relative hrefs on image nodes like on regular links"	2019-10-11 15:22:29 +00:00
ve.MWutils.js	eslint: Enable valid-jsdoc	2019-04-17 17:13:39 +01:00