lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Walter Underwood (JIRA)" <>
Subject [jira] Commented: (SOLR-127) Make Solr more friendly to external HTTP caches
Date Sat, 15 Sep 2007 04:38:32 GMT


Walter Underwood commented on SOLR-127:

Last-modified does require monotonic time, but ETags are version stamps without any ordering.
The indexVersion should be fine for an ETag.

> Make Solr more friendly to external HTTP caches
> -----------------------------------------------
>                 Key: SOLR-127
>                 URL:
>             Project: Solr
>          Issue Type: Wish
>            Reporter: Hoss Man
>         Attachments: HTTPCaching.patch, HTTPCaching.patch, HTTPCaching.patch, HTTPCaching.patch,
HTTPCaching.patch, HTTPCaching.patch
> an offhand comment I saw recently reminded me of something that really bugged me about
the serach solution i used *before* Solr -- it didn't play nicely with HTTP caches that might
be sitting in front of it.
> at the moment, Solr doesn't put in particularly usefull info in the HTTP Response headers
to aid in caching (ie: Last-Modified), responds to all HEAD requests with a 400, and doesn't
do anything special with If-Modified-Since.
> t the very least, we can set a Last-Modified based on when the current IndexReder was
open (if not the Date on the IndexReader) and use the same info to determing how to respond
to If-Modified-Since requests.
> (for the record, i think the reason this hasn't occured to me in the 2+ years i've been
using Solr, is because with the internal caching, i've yet to need to put a proxy cache in
front of Solr)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message