[
https://issues.apache.org/jira/browse/SHINDIG-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Baxter updated SHINDIG-1915:
---------------------------------
Fix Version/s: (was: 2.5.1)
2.5.2
> HttpResponses should use negativeCacheTtl for negative cache exempt statuses
> if the response has no cache-control or expires headers
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SHINDIG-1915
> URL: https://issues.apache.org/jira/browse/SHINDIG-1915
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 2.5.0-beta6
> Reporter: Stanton Sievers
> Assignee: Stanton Sievers
> Fix For: 2.5.2
>
>
> org.apache.shindig.gadgets.http.HttpResponse.getCacheExpiration() utilizes a
> list of negative-cache-exempt HTTP returns statuses that by default contains
> 401 and 403 statuses. These exempt status codes will then try to use
> Cache-Control and Expires headers to figure out how long lived the response
> should be. If no Cache-Control or Expires headers exist on the response, the
> default cache time-to-live is uses, even if the response was a 401 or 403.
> I would rather use the negative cache time-to-live in this case.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
