[
https://issues.apache.org/jira/browse/SOLR-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596468#action_12596468
]
Hoss Man commented on SOLR-574:
-------------------------------
FWIW: this is precisely why the etagSeed option is supported -- so Solr Admin's
can make the etag change even though the index hasn't changed (ie: because of
some other config changes that affect the response).
but i'm open to suggestions for new options ... the key thing being that we
want both last-Mod and Etag to be generated by default, even if there is no
<httpCaching> directive if hte solrconfig.xml
> Option to omit eTag cache (in favor of solely using last-modified)
> ------------------------------------------------------------------
>
> Key: SOLR-574
> URL: https://issues.apache.org/jira/browse/SOLR-574
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: David Smiley
> Priority: Minor
>
> I like the idea of the http caching features in 1.3 but I don't want it to
> use ETags. At least the lastModified headers are based off of a searcher
> open time but the ETags don't use this and will cause cached results to occur
> when I do things like restart the server (because I want to pick up changes
> in my new solrconfig file that affect query responses).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
