You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Marshall Shi (JIRA)" <ji...@apache.org> on 2013/02/19 06:59:12 UTC
[jira] [Updated] (SHINDIG-1904) set response cache control to -1
for JsServlet when response code is 304
[ https://issues.apache.org/jira/browse/SHINDIG-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Shi updated SHINDIG-1904:
----------------------------------
Description:
We've encountered problems that a proxy sitting in front of a Shindig server is reading the cache control to determine whether or not to cache the content in the proxy. It is problematic because the cache control max age defaults to 0 in case of 304 response code in JsServlet.
We expect the cache control indicate that the response should be cached in browser indefinitely.
The proposed fix is to set -1 as cacheTtl in the JsResponseBuilder and pass that cacheTtl value back into the JsServlet response header.
was:
We've encountered problems that a proxy sitting in front of a Shindig server is reading the cache control to determine whether or not to cache the content in the proxy. It is problematic because the cache control max age defaults to 0 in case of 304 response code in JsServlet.
We expect the cache control indicate that the response should be cached in browser indefinitely.
The proposed fix is to set -1 as cacheTtl in the JsBuilder and pass that cacheTtl value back into the JsServlet response header.
> set response cache control to -1 for JsServlet when response code is 304
> ------------------------------------------------------------------------
>
> Key: SHINDIG-1904
> URL: https://issues.apache.org/jira/browse/SHINDIG-1904
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 2.5.0-beta5
> Reporter: Marshall Shi
> Priority: Minor
> Fix For: 2.5.0-beta5
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> We've encountered problems that a proxy sitting in front of a Shindig server is reading the cache control to determine whether or not to cache the content in the proxy. It is problematic because the cache control max age defaults to 0 in case of 304 response code in JsServlet.
> We expect the cache control indicate that the response should be cached in browser indefinitely.
> The proposed fix is to set -1 as cacheTtl in the JsResponseBuilder and pass that cacheTtl value back into the JsServlet response header.
--
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