Dobromir Velev wrote:
> I'm currently investigating an issue with gzip encoded data with
> invalid ISIZE . It looks like some of the HTTP servers will randomly
> set the last four bytes of the response to 0xFFFFFFFF, instead of
> the uncompressed content size.

If it's always 0xFFFFFFFF, the workaround could at least check that
it's 0xFFFFFFFF and reject any other value.

-- Jamie

...
> 06f0: 53 bf 65 1b b7 dc 7f 53 70 f1 20 f8 12 fc d4 0d S.e...Sp. .....
> 0700: b5 11 f3 8b 90 62 cc 03 98 00 43 a3 75 98 5f 3d .....b....C.u._=
> 0710: 83 99 16 17 80 1f f0 ff 13 83 ce ff 01 fb 10 9d ................
> 0720: 56 ff ff ff ff V....
> == Info: Error while processing content unencoding: invalid code lengths set
> == Info: Closing connection #0

> 0000: 43 6f 6e 74 65 6e 74 2d 45 6e 63 6f 64 69 6e 67 Content-Encoding
> 0010: 3a 20 67 7a 69 70 0d 0a : gzip..
...
> 0000: 1f 8b 08 00 00 00 00 00 00 00 ed 3d ed 72 db 38 ...........=.r.8
> 0010: 92 bf 9d aa 79 07 0c 53 95 49 6e 4d d1 b2 63 27 ....y..S.InM..c'
> 0020: fe d2 96 2d 3b 19 cf f8 6b 6d 67 b2 73 7f 54 14 ...-;...kmg.sT.
...
> 06f0: 53 bf 65 1b b7 dc 7f 53 70 f1 20 f8 12 fc d4 0d S.e...Sp. .....
> 0700: b5 11 f3 8b 90 62 cc 03 98 00 43 a3 75 98 5f 3d .....b....C.u._=
> 0710: 83 99 16 17 80 1f f0 ff 13 83 ce ff 01 fb 10 9d ................
> 0720: 56 96 65 00 00 V.e..
> == Info: Connection #0 to host www.vmware.com left intact
> == Info: Closing connection #0
Received on 2009-08-14