You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2013/12/17 15:16:20 UTC

[Bug 55896] Secure page can be cached in browser. Cache control is not set in HTTP header nor HTML header.

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

Eric Covener <co...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 OS|                            |All

--- Comment #1 from Eric Covener <co...@gmail.com> ---
Does it happen on a contemporary maintenance level?

 A response received with any other status code (e.g. status codes 302 and 307)
MUST NOT be returned in a reply to a subsequent request unless there are
cache-control directives or another header(s) that explicitly allow it. For
example, these include the following: an Expires header (section 14.21); a
"max-age", "s-maxage", "must- revalidate", "proxy-revalidate", "public" or
"private" cache-control directive (section 14.9).

-- 
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