I was leaving it open so I could add hooks to customize the negative
caching ttl
I'll open a new issue for that...
On Jun 9, 2008, at 1:05 AM, Kevin Brown (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SHINDIG-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Brown closed SHINDIG-278.
-------------------------------
Resolution: Fixed
This has been in for a while, too.
For RemoteContentFetcher implement 504 timeouts and Negative Caching
--------------------------------------------------------------------
Key: SHINDIG-278
URL: https://issues.apache.org/jira/browse/SHINDIG-278
Project: Shindig
Issue Type: Improvement
Components: Gadget Rendering Server (Java)
Reporter: Paul Lindner
Assignee: Paul Lindner
In production we've found it necessary to negative cache failing
requests as a self preservation measure.
We also want to return a 504 response if the upstream server times
out instead of a generic 500, this helps the developer
understand that the fault lies in the network and not in Shindig.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Paul Lindner
[EMAIL PROTECTED]
