On 20 February 2013 12:11, Andre Klapper <aklapper(a)wikimedia.org> wrote: I've fixed the ones I know about, so I don't know if they'll be much help (which is why I didn't specify them before). If it does help, they were: http://en.wikipedia.org/wiki/Neil_Clark_Warren and http://en.wikipedia.org/wiki/Pepper_Schwartz (You can draw your own conclusions from my colleague's office reading habits!)

On 20 February 2013 12:43, Tim Starling <tstarling(a)wikimedia.org> wrote: Which is why I didn't bother including the URLs in the initial report. My top priority was helping the person that reported it to read the page they wanted to read. A little gratitude to someone trying to help you fix a problem wouldn't go amiss...

On Wed, Feb 20, 2013 at 9:59 AM, Sumana Harihareswara <sumanah(a)wikimedia.org> wrote: What sort of debugging information is useful depends on the situation. In most cases the type of information I mentioned would be overkill. We appreciate the bug report, we just can't do anything about it without more information. To give a (not entirely fair) comparison, imagine someone posted on your talk page that there was a spelling error on Wikipedia. I assume you would respond to such a report with "where?", it wouldn't be because you're ungrateful that you respond like that, but simply that you cannot fix the issue without more information (Wikipedia is a big place). The situation here is somewhat similar. We're grateful for the report, but would need more information before we can do anything about it. --bawolff

Sumana Harihareswara wrote: More to the point (this is a list for developers, after all), if you're a developer and you find a bug (or a potential bug!), please report it to <https://bugzilla.wikimedia.org> (aliased as <https://bugs.wikimedia.org> or <https://bugs.mediawiki.org>). :-) This list (wikitech-l) is fine for discussion of bugs (or possible bugs), but it _really helps_ when the issue can be properly tracked in Bugzilla. Mailing lists are ephemeral. Bugzilla is forever. MZMcBride

Never on wikipedia (that ive heard of) but on third party wikis - a misconfiguration causing double encoding with gzip causes symptoms very similar to what you describe. But as andre said, without an example is very difficult to say anything. If someone came across something like that again, please include as much detail as possible - save a copy of the broken page, save what http headers you got with the request (if you know how), mention if you were logged in or not, check to see if the page is always served broken or if it was just a one time thing, etc. You never know which detail might be important. -bawolff On 2013-02-20 8:11 AM, "Andre Klapper" &lt;aklapper(a)wikimedia.org&gt; wrote: