After exposing the Solr endpoint with a reverse proxy, it’s important to note that it also exposes the Solr admin panel to the end-user. This is not desired.

Flowchart of a RewriteRule directive that rests on website.com’s httpd.conf file.

Problem:

• Solr’s admin panel becomes exposed from the reverse proxy.

Solutions:

• Perform a redirect to website.com’s homepage.
• RewriteRule directive, mod_rewrite – Apache HTTP Server.

RewriteRule ^/solr/$ / [R=301,L,DPI]

It’s encouraged that you secure your Solr instance by placing the application on a different file server and behind a firewall. That’s an issue if you are trying to consume data from the Solr instance leveraging AJAX techniques.

Flowchart of a reverse proxy directive that rests on website.com’s httpd.conf file.

Problems:

• www.website.com and Apache Solr live on separate boxes.
• A firewall protecting Apache Solr plus the cross-domain issue does not expose the necessary end-point to consume via AJAX.
• Depending on your sys admin setups, Solr may not live on a fully qualified domain (ie. http://12.34.56.789:8983/solr/#/)
• An AJAX call to consume the Solr instance’s JSON/XML won’t work cross-domain.

Solution:

• Reverse Proxy directive, mod_proxy – Apache HTTP Server
• This allows for an endpoint that is visible to the browser and we can consume the JSON/XML that rests within the Solr instance.

ProxyPass /solr http://12.34.56.789:8983/solr/#/
ProxyPassReverse /solr http://12.34.56.789:8983/solr/#/

Don’t forget to apply a RewriteRule Directive to protect the Solr admin panel, once you’ve exposed it to the browser!

I’ve implemented Ben Alman’s simple-proxy.php to communicate to an Apache Solr instance (in this case my local) outside of my domain.

I’ve followed the instructions in full, the core of which is to set the simple-proxy.php on my domain’s file server.

I’m curious on if there are any modifications that must be made to the proxy in order for the response to be in the correct format?

View on Stackoverflow.