Re: svn commit: r638484 - /lucene/solr/trunk/CHANGES.txt
On Tue, Mar 18, 2008 at 2:03 PM, [EMAIL PROTECTED] wrote: +Solr now recognizes HTTP Request headers related to HTTP Caching (see +RFC 2616 sec13) and will by default respond with 304 Not Modified +when appropriate. This should only affect users who access Solr via +an HTTP Cache, It affects browsers too. I noticed that no new request was being executed when I hit refresh in firefox. I worked around it by adding a random arg like x=1234 to get it to re-execute. -Yonik
Re: svn commit: r638484 - /lucene/solr/trunk/CHANGES.txt
On Mar 18, 2008, at 3:04 PM, Yonik Seeley wrote: On Tue, Mar 18, 2008 at 2:03 PM, [EMAIL PROTECTED] wrote: +Solr now recognizes HTTP Request headers related to HTTP Caching (see +RFC 2616 sec13) and will by default respond with 304 Not Modified +when appropriate. This should only affect users who access Solr via +an HTTP Cache, It affects browsers too. I noticed that no new request was being executed when I hit refresh in firefox. I worked around it by adding a random arg like x=1234 to get it to re-execute. I experienced the same thing, but instead of a random argument you can hold down shift while clicking the reload button to have it make a fresh request. Erik
Re: svn commit: r638484 - /lucene/solr/trunk/CHANGES.txt
: +Solr now recognizes HTTP Request headers related to HTTP Caching (see : +RFC 2616 sec13) and will by default respond with 304 Not Modified : +when appropriate. This should only affect users who access Solr via : +an HTTP Cache, : : It affects browsers too. I noticed that no new request was being : executed when I hit refresh in firefox. Well, I would argue that paragraph is technically correct since you are accessing Solr via an HTTP Cache ... your browser cache. But I'll update it to make special note of that. -Hoss
