title: Reverse Proxy Solr behind Apache Web server
body: <p>I have an existing apache web server (2.2.15), configured with various security details (https only / authentication / authorization / etc.). I can rely on this server to handle the access requirements to my solr installation.</p>
  
  <p>I have a basic 'example' solr instance up and running on a separate machine. (Solr 4.8.0 )</p>
  
  <p>I want to be able to redirect the url <code>https://myserver/department/team/search/....</code> to the Solr instance running on another (private) machine <code>http://solrserver:8983/</code></p>
  
  <p>I have configured the apache server with:</p>
  
  <pre><code>ProxyPass /department/team/search/ http://solserver:8983/
  ProxyPassReverse /department/team/search/ http://solserver:8983/
  </code></pre>
  
  <p>I have some success with this, the https is being handled, the authentication/access is handled, and so on.</p>
  
  <p>When I browse to the the url it is even loading up the basic solr page, but the page, internally, has the following:</p>
  
  <pre><code>  &lt;script type="text/javascript"&gt;
  
    var app_config = {};
  
    app_config.solr_path = '\/solr';
    app_config.core_admin_path = '\/admin\/cores';
  
    &lt;/script&gt;
  </code></pre>
  
  <p>And that (I believe) is causing the JavaScript code to try to call:</p>
  
  <pre><code> https://myserver/solr/admin/cores?wt=json&amp;indexInfo=false&amp;_=1399485239437
  </code></pre>
  
  <p>Instead of</p>
  
  <pre><code> https://myserver/department/team/search/solr/admin/cores?wt=json&amp;indexInfo=false&amp;_=1399485239437
  </code></pre>
  
  <p>I believe these two values are configurable ( <code>app_config.solr_path</code> and <code>app_config.core_admin_path</code> ) but I cannot find out how/where to do it......</p>
  
  <p>Questions:</p>
  
  <ol>
  <li>How do I change the values set for the <code>app_config.solr_path</code> and <code>app_config.core_admin_path</code>?</li>
  <li>Alternatively, this may be the wrong way to do this entirely, is there a better way to do it? (though the authentication/security provided by the apache webserver is perfect right now....)</li>
  </ol>