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...
It's a bug in Safari that's "fixable" in AxKit.
Basically Safari throws that up when you send gzipped pages without a Content-Length field.
It's fixed in CVS.
Matt.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]