[SOLR-1765] HTTP Caching related headers are incorrect for distributed searches

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.4
• Assignee: Unassigned
• Reporter: Charlie Jackson
• Created: 09/Feb/10 17:50
• Updated: 10/Jul/17 10:08

Description

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