On 07/20/2011 09:44 AM, Alan D. Cabrera wrote:
I have no control over the origin.
According to the documentation it says that headers are ignored by default and
items are cached. The records.config says otherwise.
Things were changed. However, headers should never be ignored, the old
defaults used to be to require at least Last-Modified, which is per the
2616 specs, but it turns out even sites like amazon.com don't understand
HTTP, and made private content (shopping carts) cacheable with that
setting. So we tightened it down even further, and the default requires
explicit Expires or Cache-Control: max-age headers.
Setting it to 0 lets it cache "anything" that's not explicitly
disallowed to cache.
I set the
CONFIG proxy.config.http.cache.required_headers INT 0
and still nothing gets cached.
Hmmm, yeah, this is really difficult to debug with actually have either
access to your configs (including URLs, how you remap etc.), or your
system. All I can suggest is to debug with the -T tracer options (e.g.
-T http.*) and examine why it's not caching it.
-- Leif
