[ 
https://issues.apache.org/jira/browse/TS-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudheer Vinukonda updated TS-3980:
----------------------------------
    Description: 
Refer TS-3978, TS-3979

Caching of empty docs is slightly trickier on ATS, since, it is not clear 
whether the empty body is a real empty response from the Origin server or a 
consequence of broken response (connection). Currently, this is controlled via 
a config setting allow_empty_doc with additional logic such as Content-Length=0 
to make sure it's a valid empty response from Origin server. 

The current logic however misses handling valid empty response with no 
Content-Length=0 header (e.g Chunked TE, SPDY/H2 outbound etc). 

Opening jira to investigate how to *safely* (i.e ensuring the response is not a 
result of broken connection) remove the allow_empty_doc setting and to be able 
to generically cache empty docs similar to any other response. 

  was:
Refer TS-3978, TS-3979

Instead of using special config settings (e.g allow_empty_doc) to control 
caching of empty docs, the consensus is to always cache any doc that is 
cacheable and safe to cache (meaning, unbroken response, including 
Content-Length(0), Chunked Encoding (0), SPDY/H2(0) etc).


> Improve empty doc caching.
> --------------------------
>
>                 Key: TS-3980
>                 URL: https://issues.apache.org/jira/browse/TS-3980
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Cache
>            Reporter: Sudheer Vinukonda
>             Fix For: sometime
>
>
> Refer TS-3978, TS-3979
> Caching of empty docs is slightly trickier on ATS, since, it is not clear 
> whether the empty body is a real empty response from the Origin server or a 
> consequence of broken response (connection). Currently, this is controlled 
> via a config setting allow_empty_doc with additional logic such as 
> Content-Length=0 to make sure it's a valid empty response from Origin server. 
> The current logic however misses handling valid empty response with no 
> Content-Length=0 header (e.g Chunked TE, SPDY/H2 outbound etc). 
> Opening jira to investigate how to *safely* (i.e ensuring the response is not 
> a result of broken connection) remove the allow_empty_doc setting and to be 
> able to generically cache empty docs similar to any other response. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to