
varnish-bugs at varnish-cache
Apr 23, 2012, 7:46 AM
Post #1 of 6
(127 views)
Permalink
|
|
#1128: GZIP encoding with multiple members
|
|
#1128: GZIP encoding with multiple members --------------------------------------------+------------------------------- Reporter: zviratko | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.0 | Severity: normal Keywords: gzip encoding multiple streams | --------------------------------------------+------------------------------- GZIP RFC allows multiple streams to be concatenated and then decompressed as one. Varnish fails in this scenario with: {{{ FetchError c straight read_error: -1 0 (Junk after gzip data) }}} Client is served a 503. In my case, the data in question is a JSON response made from two chunks, each compressed in application and served as one response (with correct headers and length). I confirmed the data is fine, and it works fine in browsers (apart from chrome/chromium that has a bug here as well). The only solution around this not serving it compressed to varnish, or using pipe. Attached is an example that causes this bug. -- Ticket URL: <https://www.varnish-cache.org/trac/ticket/1128> Varnish <https://varnish-cache.org/> The Varnish HTTP Accelerator _______________________________________________ varnish-bugs mailing list varnish-bugs [at] varnish-cache https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs
|