reason/advantages for making Galaxy proxy using mod_rewrite instead of mod_proxy
Hi all, Sorry if this question has been asked before searched and couldn't find anyone specifically talking about this. In the Galaxy wiki under https://bitbucket.org/galaxy/galaxy-central/wiki/Config/ApacheProxy there are instructions for setting up Galaxy behind a web server proxy. I wondered what are the reasons/advantages of doing a reverse proxy using all mod_rewrite directives (as shown in the instructions) vs doing a standard Apache front-end reverse proxy: ProxyRequests Off ProxyPass / http://galaxy.host.domain:8080/ ProxyPassReverse / http://galaxy.host.domain:8080/ The instructions using mod_rewrite are making a reverse proxy too since the RewriteRule directive has the [P] flag. regards, Leandro
Hi again, After a bit more research I guess I can see why -- since as you show in the instructions you also intend to serve static content via the proxy server and this requires using mod_rewrite anyway that you chose to do the reverse proxy part also using mod_rewrite. Sorry for being confused, I have seen before configurations with mod_proxy and mod_rewrite directives together doing the same thing I was wondering why! :) best, Leandro On Fri, Apr 8, 2011 at 12:22 PM, Leandro Hermida <softdev@leandrohermida.com
wrote:
Hi all,
Sorry if this question has been asked before searched and couldn't find anyone specifically talking about this. In the Galaxy wiki under https://bitbucket.org/galaxy/galaxy-central/wiki/Config/ApacheProxy there are instructions for setting up Galaxy behind a web server proxy. I wondered what are the reasons/advantages of doing a reverse proxy using all mod_rewrite directives (as shown in the instructions) vs doing a standard Apache front-end reverse proxy:
ProxyRequests Off ProxyPass / http://galaxy.host.domain:8080/ ProxyPassReverse / http://galaxy.host.domain:8080/
The instructions using mod_rewrite are making a reverse proxy too since the RewriteRule directive has the [P] flag.
regards, Leandro
Sorry one more question... are these lines in the Galaxy wiki instructions still correct for the latest galaxy-dist? RewriteRule ^/galaxy/static/style/(.*) /home/nate/galaxy_dist/static/june_2007_style/blue/$1 [L] RewriteRule ^/galaxy/static/scripts/(.*) /home/nate/galaxy_dist/static/scripts/packed/$1 [L] best, Leandro On Fri, Apr 8, 2011 at 1:55 PM, Leandro Hermida <softdev@leandrohermida.com>wrote:
Hi again,
After a bit more research I guess I can see why -- since as you show in the instructions you also intend to serve static content via the proxy server and this requires using mod_rewrite anyway that you chose to do the reverse proxy part also using mod_rewrite. Sorry for being confused, I have seen before configurations with mod_proxy and mod_rewrite directives together doing the same thing I was wondering why! :)
best, Leandro
On Fri, Apr 8, 2011 at 12:22 PM, Leandro Hermida < softdev@leandrohermida.com> wrote:
Hi all,
Sorry if this question has been asked before searched and couldn't find anyone specifically talking about this. In the Galaxy wiki under https://bitbucket.org/galaxy/galaxy-central/wiki/Config/ApacheProxy there are instructions for setting up Galaxy behind a web server proxy. I wondered what are the reasons/advantages of doing a reverse proxy using all mod_rewrite directives (as shown in the instructions) vs doing a standard Apache front-end reverse proxy:
ProxyRequests Off ProxyPass / http://galaxy.host.domain:8080/ ProxyPassReverse / http://galaxy.host.domain:8080/
The instructions using mod_rewrite are making a reverse proxy too since the RewriteRule directive has the [P] flag.
regards, Leandro
Leandro Hermida wrote:
Sorry one more question... are these lines in the Galaxy wiki instructions still correct for the latest galaxy-dist?
They should be, yes.
RewriteRule ^/galaxy/static/style/(.*) /home/nate/galaxy_dist/static/june_2007_style/blue/$1 [L] RewriteRule ^/galaxy/static/scripts/(.*) /home/nate/galaxy_dist/static/scripts/packed/$1 [L]
best, Leandro
On Fri, Apr 8, 2011 at 1:55 PM, Leandro Hermida <softdev@leandrohermida.com>wrote:
Hi again,
After a bit more research I guess I can see why -- since as you show in the instructions you also intend to serve static content via the proxy server and this requires using mod_rewrite anyway that you chose to do the reverse proxy part also using mod_rewrite. Sorry for being confused, I have seen before configurations with mod_proxy and mod_rewrite directives together doing the same thing I was wondering why! :)
best, Leandro
On Fri, Apr 8, 2011 at 12:22 PM, Leandro Hermida < softdev@leandrohermida.com> wrote:
Hi all,
Sorry if this question has been asked before searched and couldn't find anyone specifically talking about this. In the Galaxy wiki under https://bitbucket.org/galaxy/galaxy-central/wiki/Config/ApacheProxy there are instructions for setting up Galaxy behind a web server proxy. I wondered what are the reasons/advantages of doing a reverse proxy using all mod_rewrite directives (as shown in the instructions) vs doing a standard Apache front-end reverse proxy:
ProxyRequests Off ProxyPass / http://galaxy.host.domain:8080/ ProxyPassReverse / http://galaxy.host.domain:8080/
The instructions using mod_rewrite are making a reverse proxy too since the RewriteRule directive has the [P] flag.
regards, Leandro
___________________________________________________________ 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 (2)
-
Leandro Hermida -
Nate Coraor