On Nov 30, Geoffrey Young wrote:
> I was basing that on discussions on the mod_gzip list and the following
> (from the mod_gzip code)
>
> * 5. Many browsers ( such as Netscape 4.75 for UNIX ) are unable
> * to handle Content-encoding only for specific kinds of HTML
> * transactions such as Style Sheets even though the browser
> * says it is HTTP 1.1 compliant and is suppying the standard
> * 'Accept-encoding: gzip' field. According to the IETF
> * specifications any user-agent that says it can accept
> * encodings should be able to do so for all types of HTML
> * transactions but this is simply not the current reality.
> * Some will, some won't... even if they say they can.
>
> I don't have any first hand experience with it, though...
i don't have any first-hand experience with it either (and don't
doubt at all that there are browser bugs in the implementations),
but the language of that comment is atrocious. there's no such
thing as an "html transaction". all the http/1.1 rfc (2616) has to
say on the matter is that if the browser sends an accept-encoding
header that lists an encoding type (such as gzip) with a non-zero
q-value, the server may send the response using that content-encoding.
it doesn't matter what type of data is being served (the server
could gzip gif images if it really wanted).
nothing beats just having a reasonable test environment to be able
to test the major browsers against your site. with something like
vmware, you can even use a single box to act as most of your
platforms. (you could probably even do better by having a macintosh
and using one of the virtual-intel-pc applications available for
it.)
jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
