Hi all -

There seems to be a bug in Safari / AxKit when serving gzipped pages... I'm wondering if anyone else has seen this, and what their workaround was?

The error I get in Safari 1.1 is:

Could not open the page "http://...";
The error was: "bad server response" (NSURLErrorDomain:-1011)

The kicker is that the page actually loads and renders fine! It's just a really annoying alert panel that scares users...

I did some packet-level sniffing to see what was different between the Safari response and a response to Mozilla, and they looked very similar - both received gzipped content, but the content-size was different... Which seems weird to me, I expect that to match. So maybe that's part of it?

I know AxKit has some cool logic somewhere (I haven't had time to dig for it yet) that allows gzip to do different things for different browsers, including supporting browsers that don't advertise gzip but can do it. I also know Safari didn't support gzip until 1.1, released with Panther. Is it possible this is just a Safari issue? Or maybe AxKit is confused about the new Safari claiming gzip capability?

Any thoughts appreciated!
Nate



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to