[jira] Issue Comment Edited: (SOLR-127) Make Solr more friendly to external HTTP caches

["Otis Gospodnetic (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549513 ] 

otis edited comment on SOLR-127 at 12/7/07 10:45 AM:
-----------------------------------------------------------------

I gave my vote for this one, but ant test failed for me after I applied this patch:

junit.framework.AssertionFailedError: Unknown request response expected:<0> but was:<400>
	at org.apache.solr.servlet.CacheHeaderTest.checkResponseBody(CacheHeaderTest.java:175)
	at org.apache.solr.servlet.CacheHeaderTest.doCacheControl(CacheHeaderTest.java:328)
	at org.apache.solr.servlet.CacheHeaderTest.testCacheControl(CacheHeaderTest.java:152)


      was (Author: otis):
    I gave my vote for this one, but ant test failed for me after I applied this patch.
  
> 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, 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.