always prefer to content-length rather than chunking for cacheable request

[esmq2092]

when set proxy.config.http.chunking_enabled to 3, according documentation, which means generate a chunked response if the client request is HTTP/1.1 and the origin server has previously returned HTTP/1.1.

---

for the very first request, ats will either return chunking response or add Connection: closed header ( to help client to get the correct entity size)...

when the object had cached, ats can caculate the size of cached object and set the content-lenth properly for the following request, when content-length is caculated by ats, ats will no return chunk encoding any more....

is that a intentional behavior or a bug?

[bryancall]

This is an intentional behavior. ATS doesn't trust the origin by default to send the correct content-length header.

I have always wondered if this is being over paranoid or not. It might be good to have a stat around this to get a better idea if this is really a issue.

[bryancall]

We should verify the configuration options are working correctly for the 9.0.0 release.

[mlibbey]

FWIW, we override proxy.config.http.chunking_enabled to 0 in one of our properties.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. Marking it stale to flag it for further consideration by the community.