[
https://issues.apache.org/jira/browse/TS-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom resolved TS-2016.
-------------------------------
Resolution: Duplicate
Fix Version/s: (was: 4.2.0)
After talking to Phil, I'm fairly certain this is the same problems I was
having in TS-2245. The issue is that depending on which client request is
cached first, the cached object can satisfy other requests, or it might not.
I read through the RFCs, and this is an area where the intermediary can be as
pessimistic as it likes. We choose to be very pessimistic, and TS-2245 suggests
replacing the four options that were added to a more usable "relax matching"
set of configurations.
> Vary on Accept-Encoding is broken
> ---------------------------------
>
> Key: TS-2016
> URL: https://issues.apache.org/jira/browse/TS-2016
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Phil Sorber
> Labels: C
>
> We were caching the same document twice with equivalent Accept-Encoding
> headers and ignoring the "mismatch" fixed the problem, but the code should be
> fixed to properly match.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
