Erick,
I think that should be described differently...
You need to set-up protected access for some paths.
/update is one of them.
And you could make this protected at the jetty level or using Apache proxies
and rewrites.
Probably /select should be kept open but you need to evaluate if that can
On Fri, Sep 07, 2012 at 08:50:58AM +0200, Paul Libbrecht wrote:
Erick,
I think that should be described differently...
You need to set-up protected access for some paths.
/update is one of them.
And you could make this protected at the jetty level or using Apache proxies
and rewrites.
So
Hi,
If like most people you have application server(s) in front of solr,
the simplest and most secure option is to bind solr to a local address
(192.168.* or 10.0.0.*). The app server talks to solr via the local
(a.k.a blackhole) ip address that no-one from outside can ever access
as it's not
Securing Solr pretty much universally requires that you only allow trusted
clients to access the machines directly, usually secured with a firewall
and allowed IP addresses, the admin handler is the least of your worries.
Consider if you let me ping solr directly, I can do something really
