On Friday, 7 March 2014, 8:32, Per Buer <[email protected]> wrote:
>Hi
>>
>>
>>
>>On Thu, Mar 6, 2014 at 9:16 PM, Antony Mayi <[email protected]> wrote:
>>
>>Hi,
>>>
>>>
>>>my backend is sending chunked response (~100chunks, 100bytes each). it seems
>>>varnish then sends it again using chunked encoding but only as one big
>>>chunk. the app is sort of a json streaming system and the whole point of
>>>sending the responses in chunks is for the client to be able to handle each
>>>chunk asap once they are available. unfortunately varnish cumulates it into
>>>(which means waits for) one big chunk so the whole advantage of early client
>>>processing is gone.
>>>
>>>
>>>is there any way to control this in varnish - ie. some timeouts or buffer
>>>sizes etc (not interested in piping)?
>>
>>
>>This would require streaming. Varnish 3.0 will wait for the whole object to
>>arrive before forwarding it. Use Varnish 4.0 or dig out the streaming
>>patches. Set do_stream = true.
>>
>>
>
>
>ok, thanks for explaining. I found this:
>https://www.varnish-software.com/blog/streaming-varnish-30 which suggest it
>should work in Varnish 3.0. I am using the official 3.0.5 from varnish rpm
>repo. I am setting the do_stream to true but still getting one big chunk. so
>is the blogpost wrong or has it not been officially released as rpm yet?
>thanks,
>Antony.
_______________________________________________
varnish-misc mailing list
[email protected]
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
