The Jetty servlet container that Solr uses doesn't understand those
files. It would not use them to determine access, and would likely make
them accessible to web requests in plain text.
On 1/6/15 16:01, Craig Hoffman wrote:
Thanks Otis. Do think a .htaccess / .passwd file in the Solr
Thanks Otis. Do think a .htaccess / .passwd file in the Solr admin dir would
interfere with its operation?
--
Craig Hoffman
w: http://www.craighoffmanphotography.com
FB: www.facebook.com/CraigHoffmanPhotography
TW: https://twitter.com/craiglhoffman
> On Jan 6, 2015, at 1:09 PM, O
Hi Craig,
If you want to protect Solr, put it behind something like Apache / Nginx /
HAProxy and put .htaccess at that level, in front of Solr.
Or try something like
http://blog.jelastic.com/2013/06/17/secure-access-to-your-jetty-web-application/
Otis
--
Monitoring * Alerting * Anomaly Detection
Craig,
1. What is .htaccess file meant for?
2. What are the contents inside this file?
3. How will you or how Solr knows that it needs to look for this file to
bring in the needed security to this (which) area?
4. What event is causing for you to re-index the engine
Hi,
Your message seems quite confused (even the URL is not right for most
normal Solr setup), and it is not clear as to what you mean by "function
properly". Solr is a search engine, and has no idea about .htacess files.
Are you asking whether Solr respects directives in .htaccess f
Quick question: If put a .htaccess file in www.mydomin.com/8983/solr/#/ will
Solr continue to function properly? One thing to note, I will have a CRON job
that runs nightly that re-indexes the engine. In a nutshell I’m looking for a
way to secure this area.
Thanks,
Craig
--
Craig Hoffman
w
Quick question: If put a .htaccess file in www.mydomin.com/8983/solr/#/ will
Solr continue to function properly? One thing to note, I will have a CRON job
that runs nightly that re-indexes the engine. In a nutshell I’m looking for a
way to secure this area.
Thanks,
Craig
--
Craig Hoffman
w
