You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Stanton Sievers (JIRA)" <ji...@apache.org> on 2013/02/25 13:38:13 UTC

[jira] [Resolved] (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 ]

Stanton Sievers resolved SHINDIG-1904.
--------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.5.0-beta5)
                   2.5.0-beta6
         Assignee: Stanton Sievers

Committed revision 1449683.
                
> 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
>            Assignee: Stanton Sievers
>            Priority: Minor
>             Fix For: 2.5.0-beta6
>
>         Attachments: SHINDIG-1904.patch, w3.patch
>
>   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