Re: Solr Security and XSRF

2008-06-29 Thread Noble Paul നോബിള്‍ नोब्ळ्
SOLR-607 is still open.Till it is committed this solution may not be poossible --Noble On Mon, Jun 30, 2008 at 10:23 AM, Noble Paul നോബിള്‍ नोब्ळ् <[EMAIL PROTECTED]> wrote: > If you have a master slave configuration I guess it is a good idea to > remove the updatehandler altogether from slaves. >

Re: Solr Security and XSRF

2008-06-29 Thread Noble Paul നോബിള്‍ नोब्ळ्
If you have a master slave configuration I guess it is a good idea to remove the updatehandler altogether from slaves. --Noble On Sat, Jun 28, 2008 at 2:39 AM, Chris Hostetter <[EMAIL PROTECTED]> wrote: > > : > A basic technique that can be used to mitigate the risk of a possible CSRF > : > attack

Re: Solr Security and XSRF

2008-06-27 Thread Chris Hostetter
: > A basic technique that can be used to mitigate the risk of a possible CSRF : > attack like this is to configure your Servlet Container so that access to : > paths which can modify the index (ie: /update, /update/csv, etc...) are : > restricted either to specific client IPs, or using HTTP Authe

Re: Solr Security and XSRF

2008-06-26 Thread Christian Vogler
On Fri, Jun 27, 2008 at 1:54 AM, Chris Hostetter <[EMAIL PROTECTED]> wrote: > A basic technique that can be used to mitigate the risk of a possible CSRF > attack like this is to configure your Servlet Container so that access to > paths which can modify the index (ie: /update, /update/csv, etc...)