On 2005.02.28, Eric Lee <[EMAIL PROTECTED]> wrote:
> OK, that may explain IE 5.5, which is admittedly kind of an antique.
> What about IE 6.0 - not broken but is it in fact incapable of handling
> compressed input?
> >From my post:
> >Browser  ACCEPT_ENCODING  off/Disp:len  on/Disp:len
> >IE 5.5  gzip, deflate   yes:247   no:210
> >IE 6.0  deflate   yes:247   yes:247

Can you sniff the network and see if IE 6.0 is sending the
"Accept-Encoding:" header as part of its HTTP request?

> Apache docs on it's approach to compression at
> http://httpd.apache.org/docs-2.0/mod/mod_deflate.html seem to say they
> do additional vetting of browsers before deciding to send something
> compressed.

Yeah, in the end, our compression support will need to jump through an
equal amount of hoops to do this right: that's per-request overhead if
the client claims (accurately or not) that they support compression.
For Apache, it's probably no big deal since it's just a few more
milliseconds of latency per request on top of an already slow
(relatively speaking) model ... but for AOLserver, the impact could be
measurable.  Then again, maybe not: I haven't really tried to measure it

> A good deal of the pressure on me to do this is coming from my ISP
> whose lines are getting overloaded. As I understand it, this affects
> everyone who comes to my server, not just narrowband users.  Perhaps
> I've just outgrown this ISP?

>From the sounds of it, I'd say so.

-- Dossy

Dossy Shiobara                       mail: [EMAIL PROTECTED]
Panoptic Computer Network             web: http://www.panoptic.com/
  "He realized the fastest way to change is to laugh at your own
    folly -- then you can let go and quickly move on." (p. 70)

AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to