: on a given port, say :8983. I have my firewall (iptables) set up so
: that the outside world cannot connect to :8983. However, my httpd
: server, running on port 80, can connect to solr because they are
: running on the same box. Therefore all access to solr is mediated
: through whatever applica
m: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 11:18 AM
To: solr-user@lucene.apache.org
Subject: Re: Restrict Servlet Access
On Mar 14, 2007, at 11:09 AM, Brian Whitman wrote:
The recommendation is to firewall off Solr so only your
application server can access it. S
nt for the naivety.
-Andrew
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 11:18 AM
To: solr-user@lucene.apache.org
Subject: Re: Restrict Servlet Access
On Mar 14, 2007, at 11:09 AM, Brian Whitman wrote:
>>
>> The recommendat
Gunther, Andrew wrote:
What are people doing to restrict UpdateServlet access on production
installs of Solr. Are people removing that option and rotating in a new
index or restricting access from the jetty side.
I'm putting Solr on my DMZ without direct WAN access. If I had to put it
on
On Mar 14, 2007, at 11:09 AM, Brian Whitman wrote:
The recommendation is to firewall off Solr so only your
application server can access it. Solr is not at all designed
for direct client (browser, etc) access.
Assuming you lock down update properly, what's the problem? We are
current
The recommendation is to firewall off Solr so only your application
server can access it. Solr is not at all designed for direct
client (browser, etc) access.
Assuming you lock down update properly, what's the problem? We are
currently using select directly through the XSLTResponseWrite
On Mar 14, 2007, at 10:12 AM, Gunther, Andrew wrote:
What are people doing to restrict UpdateServlet access on production
installs of Solr. Are people removing that option and rotating in
a new
index or restricting access from the jetty side.
The recommendation is to firewall off Solr so o
What are people doing to restrict UpdateServlet access on production
installs of Solr. Are people removing that option and rotating in a new
index or restricting access from the jetty side.
Cheers,
Andrew
