How does Traffic Server handle Chunked-Transfer encoded content?

I see in the docs the setting for proxy.config.http.chunking_enabled but
have some additional questions.

1) Is the chunk size cached as part of the content? Will ATS always use the
exact same chunk size in the client response or can this be modified?

2) How long will Traffic Server keep a connection to the origin server for
pending additional chunks?

3) In the docs, what does pipelining mean? Does it mean that multiple
connections are made from a cache to the origin server to avoid blocking
other requests?

Thanks,
Eric

Reply via email to