List Info

Thread: Updated: (SOLR-127) Make Solr more friendly to external HTTP caches




Updated: (SOLR-127) Make Solr more friendly to external HTTP caches
country flaguser name
United States
2007-10-19 09:05:50
     [ 
https://issues.apache.org/jira/browse/SOLR-127?page=com.atla
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Peuss updated SOLR-127:
------------------------------

    Attachment: HTTPCaching.patch

Updated patch inspired by Hoss Mans comments.

Changes:
* Cache header settings can now be set per request handler.
Omitting the parameters switches off cache header generation
(fall back to old behaviour).
** <int
name="httpCacheLivetime">0</int>: Set
"freshness" timespan in seconds
** <bool
name="httpCacheForceRevalidation">true</bool
>: controls if we emit "must-revalidate"
** <bool
name="httpCacheForcePrivate">false</bool>
: constrols if we emit "private"
* Some refactoring to make the Filter class smaller
* Updated testcase to check that we do not emit cache
headers on POST requests.

> Make Solr more friendly to external HTTP caches
> -----------------------------------------------
>
>                 Key: SOLR-127
>                 URL: https:
//issues.apache.org/jira/browse/SOLR-127
>             Project: Solr
>          Issue Type: Wish
>            Reporter: Hoss Man
>             Fix For: 1.3
>
>         Attachments: HTTPCaching.patch,
HTTPCaching.patch, HTTPCaching.patch, HTTPCaching.patch,
HTTPCaching.patch, HTTPCaching.patch, 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.


[1]

about | contact  Other archives ( Real Estate discussion Medical topics )