[
https://issues.apache.org/jira/browse/SOLR-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080096#comment-16080096
]
Jan Høydahl commented on SOLR-1765:
-----------------------------------
Is this still a problem? (Have not checked the source)
> HTTP Caching related headers are incorrect for distributed searches
> -------------------------------------------------------------------
>
> Key: SOLR-1765
> URL: https://issues.apache.org/jira/browse/SOLR-1765
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Charlie Jackson
> Priority: Minor
>
> When searching across multiple shards with HTTP caching enabled, the Caching
> related headers (ETag, Cache-Control, Last-Modified) in the response are
> based on the "index" of the coordinating solr core, and are not influenced by
> the properties of the shards. For example, take the query
> http://localhost:8983/solr/core1/select/?q=google&shards=localhost:8983/solr/core2,localhost:8983/solr/core3
> ETag should be calculated off of core2 and core3, instead it's being
> calculated from the index of core1.
> This results in index modificaitons to to core2 or core3 being "invisible" to
> clients which query this URL using "If-None-Match" or "If-Modified-Since"
> type requests
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
