Last modified: 2012-07-19 18:26:48 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 4635 - Workaround for Safari '.gz' extension bug
Workaround for Safari '.gz' extension bug
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
Macintosh Mac OS X 10.4
: Normal minor with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-01-17 00:05 UTC by Brion Vibber
Modified: 2012-07-19 18:26 UTC (History)
0 users

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


Description Brion Vibber 2006-01-17 00:05:15 UTC
The latest updates to Safari in Mac OS X 10.4.4 seem to have broken loading of 
pages that have a ".gz" extension when they're sent with gzip encoding.

The browser downloads the gzipped text to a file instead of displaying it 
inline. This is clearly a bug in either Safari itself or WebKit; I'll 
investigate and file bugs/patches to Apple.

In the meantime, we might consider as a workaround sending pages whose URLs 
end in '.gz' without compression. Yucky hack, but seems to work in my testing.

(Possibly refile this under Wikimedia, if we don't want such a hack polluting 
the main software. An if() in CommonSettings will do the job.)
Comment 1 Brion Vibber 2006-01-17 00:32:11 UTC
Added hack in CommonSettings.php like this:

# Safari bug with URLs ending in ".gz" and gzip encoding
$hatesSafari = isset( $_SERVER['PATH_INFO'] ) &&
    strtolower( substr( $_SERVER['PATH_INFO'], -3 ) ) == '.gz';

then check that var before adding the buffering handler.

Marking this FIXED since I've worked around it, still investigating to 
make sure it's reported back to Apple.
Comment 2 Brion Vibber 2006-01-17 01:52:19 UTC
Haven't found the source of the problem in WebKit source yet, but can
confirm that I can't correctly visit pages which would exhibit this
bug in Safari in a quickie WebKit-based Xcode project. So it doesn't
seem to be the Safari front-end code, but lower-level where I might
be able to locate it...
Comment 3 Brion Vibber 2006-01-17 03:50:19 UTC
Alas, it seems to be even lower-level than WebKit/WebCore, so out of my reach 
again. :)

As recommended by the folks in #webkit, I've filed a bug with Apple.
Radar problem ID 4410917.
Comment 4 Sam Reed (reedy) 2012-07-17 11:45:43 UTC
Do we still need this hack in our settings? Is 6 years enough time to hope everyone is running a newer version? I guess in the Apple world that's even more likely...
Comment 5 Brion Vibber 2012-07-19 18:26:48 UTC
It's probably safe to ditch this, but test first. :)

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