Hi everyone.

First off, it goes without saying that apachesolr is awesome and very fast. We have it setup and working and our database load has dropped from around 2-3 to .5. We have lots of searches.

Here is our issue, we have a flash app, my thought was to expose solr to flash, allowing the flash app to query solr. The downside to this is, anyone can run update or delete requests if they can figure out the URL.

So I have 3 options:

1) put solr behind apache with mod proxy or the like, and use apache to block ip requests to update and delete requests.

2) build a simple drupal module that acts as a proxy server. This would allow me to log and have more fine grain control over requests but would also slow down the searches (boot strap drupal) .

3) build a simple standalone php script that just acts as a proxy server, doing what #1 does but in php code.

What are others doing?

Thanks

Comments

Scott Reynolds’s picture

Scott Reynolds commented

We do #3 for our Javascript searches.

And the reason was simple, we could build it quick and we could do it with out having to install more software on our developers machines.

drupalnuts’s picture

drupalnuts commented

Scott, can you share your code?

HonorsGrad’s picture

HonorsGrad commented

Subscribe

jpmckinney’s picture

jpmckinney commented
Status: Active » Fixed

Here is a very simple PHP proxy (per #3): http://gist.github.com/298580

For #1, you can configure Tomcat to prevent certain queries. You can find lots of information for that online and on the Solr mailing lists. Here's one blog post, for example: http://blog.comtaste.com/2009/02/securing_your_solr_server_on_t.html

For #2, I wouldn't recommend it, but you can probably build something based off of the proxy above.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.