Last modified: 2009-03-09 23:24:42 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 T18230, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16230 - Page always delivered using gzip compression in HTTP
Page always delivered using gzip compression in HTTP
Status: RESOLVED DUPLICATE of bug 7098
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://de.wikipedia.org/wiki/Demonstr...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-03 16:50 UTC by Gideon Greenspan
Modified: 2009-03-09 23:24 UTC (History)
1 user (show)

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


Attachments

Description Gideon Greenspan 2008-11-03 16:50:20 UTC
When this page is requested, it seems to be delivered using gzip compression in the HTTP protocol, even if the client has not specified that they accept gzip compression. I found this problem when a user of my Copyscape service reported the page was coming up as gibberish in Copyscape. I've also confirmed it using the Rex Swain HTTP viewer here (http://www.rexswain.com/httpview.html) I thought you might want to know in case it reflects some broader (caching?) issue.
Comment 1 Brion Vibber 2008-11-03 17:32:18 UTC
We've seen a few of these here and there, but haven't been able to reproduce the actual cause.

Pages seem to get stuck in the cache with wrong compression...

HEAD http://de.wikipedia.org/wiki/Demonstrationen_in_Tibet_2008 HTTP/1.0
Host: de.wikipedia.org
User-Agent: testing

HTTP/1.0 200 OK
Date: Sun, 02 Nov 2008 15:40:43 GMT
Server: Apache
X-Powered-By: PHP/5.2.4-2ubuntu5wm1
Cache-Control: private, s-maxage=0, max-age=0, must-revalidate
Content-Language: de
Vary: Accept-Encoding,Cookie
X-Vary-Options: Accept-Encoding;list-contains=gzip,Cookie;string-contains=dewikiToken;string-contains=dewikiLoggedOut;string-contains=dewiki_session;string-contains=centralauth_Token;string-contains=centralauth_Session;string-contains=centralauth_LoggedOut
Last-Modified: Fri, 31 Oct 2008 22:46:09 GMT
Content-Encoding: gzip
Content-Length: 21077
Content-Type: text/html; charset=utf-8
Age: 92944
X-Cache: HIT from sq20.wikimedia.org
X-Cache-Lookup: HIT from sq20.wikimedia.org:3128
X-Cache: MISS from sq31.wikimedia.org
X-Cache-Lookup: MISS from sq31.wikimedia.org:80
Via: 1.0 sq20.wikimedia.org:3128 (squid/2.6.STABLE21), 1.0 sq31.wikimedia.org:80 (squid/2.6.STABLE21)
Connection: close

So either:

* Squid is mistakenly caching a gzip-requested response for non-gzip-requestors

or

* PHP/MediaWiki is mistakenly gzipping a response for non-gzip-requestors, which Squid dutifully caches.

It's intermittent and we haven't been able to reproduce the conditions causing it on demand. Might be worth double-checking the PHP gzhandler stuff to make sure its conditions are correct.
Comment 2 Marcin Cieślak 2009-01-06 00:54:18 UTC
I have seen this again today. http://pl.wikipedia.org/wiki/Template:GeoTemplate got served gzipped. 

This edit fixed this: http://pl.wikipedia.org/w/index.php?title=Szablon%3AGeoTemplate&diff=15439485&oldid=14665146

According to the Squid mailing list (see http://www.mail-archive.com/squid-users@squid-cache.org/msg59375.html) Squid does not support gzipping response for non-gzip-requestors (there is an add-one project to do this: http://devel.squid-cache.org/projects.html#gzip).

So, unless we mess with the Squid source, I would rule Squid out.

Comment 3 Marcin Cieślak 2009-01-06 02:56:18 UTC
A discussion in bug 7098 seems to be related to this issue.
Comment 4 Brion Vibber 2009-03-09 23:24:42 UTC

*** This bug has been marked as a duplicate of bug 7098 ***

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


Navigation
Links