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/06/02 15:35:19 UTC

[jira] [Created] (SHINDIG-1920) Don't force cache time-to-lives on responses with an error status

Stanton Sievers created SHINDIG-1920:
----------------------------------------

             Summary: Don't force cache time-to-lives on responses with an error status
                 Key: SHINDIG-1920
                 URL: https://issues.apache.org/jira/browse/SHINDIG-1920
             Project: Shindig
          Issue Type: Bug
          Components: Java
    Affects Versions: 2.5.0-beta6
            Reporter: Stanton Sievers
            Assignee: Stanton Sievers
             Fix For: 2.5.0


org.apache.shindig.gadgets.DefaultGadgetSpecFactory and org.apache.shindig.gadgets.DefaultMessageBundleFactory utilize a property in shindig.properties (shindig.cache.xml.refreshInterval) to force the RequestPipeline/Fetcher layer to cache specs and message bundles for a set amount of time, regardless of the cache headers on the response.  This also forces the cache ttl in the case that the response is an error instead of using the "shindig.cache.http.negativeCacheTtl" value in shindig.properties, which defaults to one minute.

I'd rather we always use the negativeCacheTtl in this case and ignore the forced cache ttl

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