bneradt commented on issue #7880: URL: https://github.com/apache/trafficserver/issues/7880#issuecomment-850529776
Recording this now so I don't forget: in an offline conversation with @bryancall, he points out that we should look into why ATS is replying with chunk encoded content in the first place for this scenario. When we serve from the cache as a fresh resource we do a content-length reply. As we are seeing with this issue, when we reply from the cache with a stale resource via the negative revalidating feature, we are serving chunk encoded. At least theoretically we should be able to reply with a content-length for the latter case as well as with the former. And we should reply with content-length bodies if we can because body communicated via content-length has parsing and preparatory advantages for the client. Thus there are two things that should be considered when implementing a fix for this issue: 1. Under some circumstances, we incorrectly truncate our chunk encoded response when we serve from the cache. 2. It would be preferable for us to serve content-length responses when responding via the negative revalidating feature. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
