[
https://issues.apache.org/jira/browse/TAP5-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thiago H. de Paula Figueiredo updated TAP5-2275:
------------------------------------------------
Summary: Kaptcha setting invalid caching response headers (was: invalid
caching response headers)
> Kaptcha setting invalid caching response headers
> ------------------------------------------------
>
> Key: TAP5-2275
> URL: https://issues.apache.org/jira/browse/TAP5-2275
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-kaptcha
> Affects Versions: 5.3.7
> Reporter: Ilya Obshadko
> Assignee: Thiago H. de Paula Figueiredo
> Labels: month-of-tapestry
> Fix For: 5.4
>
>
> please check this issue at Google Code:
> https://code.google.com/p/kaptcha/issues/detail?id=72
> There are two subsequent calls to setHeader() and second call is overriding
> the first one (that is already mentioned in code comments). Either support
> for addHeader () is needed in Response, or we need to inject
> HttpServletResponse directly.
> response.setDateHeader("Expires", 0);
> // Set standard HTTP/1.1 no-cache headers.
> response.setHeader("Cache-Control", "no-store, no-cache,
> must-revalidate");
> // Set IE extended HTTP/1.1 no-cache headers (use addHeader).
> response.setHeader("Cache-Control", "post-check=0, pre-check=0");
> // Set standard HTTP/1.0 no-cache header.
> response.setHeader("Pragma", "no-cache");
> Expires: 0 is still enough for all browsers except Firefox, which doesn't
> reload the image, and the whole component becomes unusable.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
