Apache proxy to Galaxy: mod_rewrite or mod_proxy ?
Hi, Currently, the guide lines for using Apache as a reverse proxy to galaxy are to use the mod_rewrite module and the rewrite rules as explained in the galaxy wiki. I was wondering whether anybody has tried to use mod_proxy, mod_proxy-http instead, with proxypass and proxypassreverse directives ? any technical limitations ? could it be more efficient in a production configuration ? Thanks for the info Chris -- ¡ Note that my email address has changed ! ¡ Please update your records with ! ¡ *christophe.antoniewski@snv.jussieu.fr*<christophe.antoniewski@snv.jussieu.fr>! -- Christophe Antoniewski Drosophila Genetics and Epigenetics Laboratoire de Biolologie du Développement 9, Quai St Bernard, Boîte courrier 24 75252 Paris Cedex 05 Tel +33 1 44 27 34 39 Fax +33 1 44 27 34 45 Mobile +33 6 68 60 51 50 http://drosophile.org
On Oct 18, 2012, at 12:28 PM, Christophe Antoniewski <christophe.antoniewski@snv.jussieu.fr> wrote:
Hi,
Currently, the guide lines for using Apache as a reverse proxy to galaxy are to use the mod_rewrite module and the rewrite rules as explained in the galaxy wiki.
I was wondering whether anybody has tried to use mod_proxy, mod_proxy-http instead, with proxypass and proxypassreverse directives ? any technical limitations ? could it be more efficient in a production configuration ?
Thanks for the info
Chris
Hi Chris, Here's our production config. We use external auth, which is why REMOTE_USER is set. I hope it helps. Regards, Alex <Proxy balancer://galaxy> BalancerMember http://localhost:8090 BalancerMember http://localhost:8091 BalancerMember http://localhost:8092 BalancerMember http://localhost:8093 BalancerMember http://localhost:8094 BalancerMember http://localhost:8095 BalancerMember http://localhost:8096 </Proxy> ProxyPass / balancer://galaxy/ RewriteCond %{IS_SUBREQ} ^false$ RewriteCond %{LA-U:REMOTE_USER} (.+) RewriteRule . - [E=RU:%1] RequestHeader set REMOTE_USER %{RU}e RequestHeader unset Authorization SetOutputFilter DEFLATE SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-vary SetEnvIfNoCase Request_URI \.(?:t?gz|zip|bz2)$ no-gzip dont-vary XSendFile on XSendFilePath / RewriteRule ^/static/style/(.*) /galaxy/run/prod/static/june_2007_style/blue/$1 [L] RewriteRule ^/static/scripts/(.*) /galaxy/run/prod/static/scripts/packed/$1 [L] RewriteRule ^/static/(.*) /galaxy/run/prod/static/$1 [L] RewriteRule ^/images/(.*) /galaxy/run/prod/static/images/$1 [L] RewriteRule ^/favicon.ico /galaxy/run/prod/static/favicon.ico [L] RewriteRule ^/robots.txt /galaxy/run/prod/static/robots.txt [L] RewriteRule ^/errors/(.*) /var/www/html/galaxy/errors/$1 [L]
On Oct 18, 2012, at 12:28 PM, Christophe Antoniewski wrote:
Hi,
Currently, the guide lines for using Apache as a reverse proxy to galaxy are to use the mod_rewrite module and the rewrite rules as explained in the galaxy wiki.
I was wondering whether anybody has tried to use mod_proxy, mod_proxy-http instead, with proxypass and proxypassreverse directives ? any technical limitations ? could it be more efficient in a production configuration ?
Hi Chris, My recollection is that the rewrite rule with a [P] flag effectively does the same thing as the mod_proxy directives. They both end up using mod_proxy. The rewrite rules for static will have to be traversed on every request regardless of which method you use. --nate
Thanks for the info
Chris
-- ¡ Note that my email address has changed ! ¡ Please update your records with ! ¡ christophe.antoniewski@snv.jussieu.fr !
--
Christophe Antoniewski Drosophila Genetics and Epigenetics Laboratoire de Biolologie du Développement
9, Quai St Bernard, Boîte courrier 24 75252 Paris Cedex 05
Tel +33 1 44 27 34 39 Fax +33 1 44 27 34 45 Mobile +33 6 68 60 51 50
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
participants (3)
-
Christophe Antoniewski
-
Nate Coraor
-
Oleksandr Moskalenko