Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The following page has been changed by HossMan: http://wiki.apache.org/solr/SolrConfigXml ------------------------------------------------------------------------------ <!> ["Solr1.3"] - Within the main Request Dipatcher section, the HTTP Caching subsection contains configuration options for controlling how the Solr Request Dispatcher responds to HTTP Requests that include cache validation headers, and what kinds of responses Solr will generate. + Within the main Request Dipatcher section, the HTTP Caching subsection contains configuration options for controlling how the Solr Request Dispatcher responds to HTTP Requests that include cache validation headers, and what kinds of responses Solr will generate. More information can be found in ["SolrAndHTTPCaches"] {{{ ... @@ -316, +316 @@ </requestDispatcher> }}} - The value for ''max-age'' depends on how often your index changes and how long your application can live with an outdated cached response. To force a shared (or browser) cache to recheck that the cached response is still valid you can add the parameter ''must-revalidate'' to the Cache-Control header. According to the W3C specification ''max-age'' should not be higher than 31536000 (1 year). + The value for ''max-age'' should be set based on how often your index changes and how long your application can live with an outdated cached response. To force a shared (or browser) cache to recheck that the cached response is still valid you can add the parameter ''must-revalidate'' to the Cache-Control header. According to the W3C specification ''max-age'' should not be higher than 31536000 (1 year). == Request Handler Plug-in Section ==
