Internet Explorer HTTP Compression Data Loss

  • Thread starter Thread starter Kornél Pál
  • Start date Start date
K

Kornél Pál

Hi,

I'm using HTTP compression with my ASP.NET application but I know that there
was a bug in Internet Explorer.

I've read Q312496 and Q313712 on support.microsoft.com.

However I don't know whether the 2048 bytes are lost from the compressed or
the uncompressed data.
This is important because I want to add padding to work around this bug.

If it's lost from the uncompressed data the solution is easy (padding with
spaces) and the compressed data will not be much longer.

But if it's lost from the compressed data it's difficult to pad and may not
be possible because of the header structures in the compressed stream.

I think you should add this information to the above articles as I think the
answer is not ambigous.

I want to add the padding if the User-Agent header contains MSIE 5.5 or MSIE
6.0 and not MSIE 6.0 with SV1.

As I know not other versions are affected by this bug. Am I right?

Sincererly,
Kornél
 
Does anyone know the answer? Or should I ask this in antoher newsgroup?

Sincererly,
Kornél
 
I ~suspect~ that it's 2048 bytes AFTER decompression. If you visit
www.redlinenetworks.com and look at their output in a HTTP Debugger (e.g.
http://www.fiddlertool.com) you can see that they pad with 4096 bytes of
spaces, which compress to well under 2kb.

--
Thanks,

Eric Lawrence
Program Manager
Internet Explorer Trust

This posting is provided "AS IS" with no warranties, and confers no rights.
 
If you make sure that it's true, please update KB articles as well.
Thanks.

Sincererly,
Kornél
 
Back
Top