In message <[email protected]>, Andr ea Campi writes:
>Long story short, I finally realized the problem is not with Varnish >per se, but with the office proxy (Squid 2.7.STABLE9); it seems to >corrupt the gzip stream just after the 00 00 FF FF sequence: > >-0004340 5d 90 4a 4e 4e 00 00 00 00 ff ff ec 3d db 72 dc >+0004340 5d 90 4a 4e 4e 00 00 00 00 ff ff 00 3d db 72 dc > >-0024040 75 21 aa 39 01 00 00 00 ff ff d4 59 db 52 23 39 >+0024040 75 21 aa 39 01 00 00 00 ff ff 00 59 db 52 23 39 > >and so on. We found a similar issue in ngnix last week: A 1 byte chunked encoding get zap'ed to 0x00 just like what you show. Are you sure there is no ngnix instance involved ? It would be weird of both squid and ngnix has the same bug ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ varnish-misc mailing list [email protected] http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
