[
https://issues.apache.org/jira/browse/TS-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257197#comment-13257197
]
John Plevyak commented on TS-621:
---------------------------------
weijin, your patch relies on the Content-Length: header. That is probably
safe and covers most situations, but I don't know that it will work in all
situations. Old school servers (1.0) which don't use Content-Length: will not
benefit. I have to admit that it does finesse the compatibility issues, but I
was hoping for a "complete" solution. Perhaps we can look at using some
combination of the patches whereby we use the API changes I am proposing and
verify that we are doing the right thing with the Content-Length and perhaps
use your flag?
I'll look into it as well.
> writing 0 bytes to the HTTP cache means only update the header... need a new
> API: update_header_only() to allow 0 byte files to be cached
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TS-621
> URL: https://issues.apache.org/jira/browse/TS-621
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache
> Affects Versions: 2.1.5
> Reporter: John Plevyak
> Assignee: weijin
> Fix For: 3.1.4
>
> Attachments: TS-621_cluster_zero_size_objects.patch,
> force_empty.diff, ts-621-jp-1.patch, ts-621-jp-2.patch, ts-621-jp-3.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
