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
..
ApiVisualEditor.php	Detect mangled etags from RESTBase and retry via MediaWiki API	2019-10-16 19:53:43 +02:00
ApiVisualEditorEdit.php	build: Upgrade mediawiki-codesniffer to v28.0.0	2019-10-11 12:42:23 -07:00
SpecialCollabPad.php	SpecialCollabPad: Remove unused variable $request	2019-04-01 23:08:02 +01:00
VisualEditorDataModule.php	Support for defined template context items	2019-08-30 13:02:47 +01:00
VisualEditorDesktopArticleTargetInitModule.php	Replace usage of deprecated ConfigFactory::getDefaultInstance()	2019-05-04 22:02:29 +01:00
VisualEditorHooks.php	Fix loading icons for historical diff mode switcher	2019-10-01 03:31:27 +02:00