[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-httpd-bugs
Subject:    [Bug 55669] Mod_Cache caching 503 Errors
From:       bugzilla () apache ! org
Date:       2014-11-24 22:09:47
Message-ID: bug-55669-7868-noTSgZI4dV () https ! issues ! apache ! org/bugzilla/
[Download RAW message or body]

https://issues.apache.org/bugzilla/show_bug.cgi?id=55669

Tod Schmidt <tschmidty@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #19 from Tod Schmidt <tschmidty@yahoo.com> ---
Argh, you are exactly right (of course). Sorry, was a long day. We did use
expires but had changed it to set the cache-control using the headers module so
we could set some other cache-control values as well. So expires is never
called in this case although it does apply for the other users on this thread. 

In my case, I suppose the workaround is the way to go. The confusing thing for
me was just not understanding that the headers were being applied on the proxy
server before the cache/no-cache decision was made.

So something like this:

Header set Cache-Control public,max-age=1800 "expr=%{REQUEST_STATUS} == '200'"

or 

Header set Cache-Control public,max-age=1800 "expr=%{REQUEST_STATUS} != '503'"

Would work in my situation. Thanks for your response and sorry to have
erroneously reopened this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]