I moved the RewriteRules statements outside the <location> block
and now it is working.

Thank you.

On Fri, Aug 5, 2011 at 11:57 AM, Assaf Gordon <gordon@cshl.edu> wrote:
Your "rewrite" rules are not taking affect (as evident by the fact that apache is looking for a folder named "galaxy" in your document root folder (/usr/local/apache/htdocs/).

First thing to try is to take the "RewriteRules" statements outside the "<location>" block.

Then, enable mod_rewrite logging with the following two statements:
 RewriteLog /tmp/rewrite.log
 RewriteLogLevel 9

and restart apache.
you'll then see every URL access in "/tmp/rewrite.log", and whether mod_rewrite handled it or not.

-gordon


Jennifer Jackson wrote, On 08/05/2011 11:46 AM:
> Hello,
>
> I am going to move this over to the galaxy-dev list so that the larger development community can more easily access your question and provide some feedback.
>
> Thanks!
>
> Jen
> Galaxy team
>
> On 8/4/11 12:55 PM, Sridhar A Malkaram wrote:
>> Hi,
>>
>> I have been using galaxy succesfully for my work using its internal
>> web-server. Recently I wanted to use it over the internet and so, I
>> configured it with apache at /galaxy of apache's root. I followed all
>> the instructions in setting up the proxy redirection. But I think the
>> re-direction is not happening. I highly appreciate any suggestions to
>> correct the issue.
>>
>> I checked for the mod_proxy, mod_proxy_http etc modules and they are
>> present and switched on.
>>
>> Apache gives the following error in its error_log file:
>>
>> [Thu Aug 04 14:15:56 2011] [error] [client 127.0.0.1] File does not
>> exist: /usr/local/apache/htdocs/galaxy
>>
>> Galaxy was set up in the directory /home/galaxy/galaxy-dist
>> The lines specific for proxy setting in  universe_wsgi.ini  are as follows:
>> use = egg:Paste#http
>> port = 8080
>> host = localhost
>> [filter:proxy-prefix]
>> use = egg:PasteDeploy#prefix
>> prefix = /galaxy
>> [app:main]
>> filter-with = proxy-prefix
>> cookie_path = /galaxy
>> use_remote_user = True
>> remote_user_maildomain = unl.edu <http://unl.edu>
>>
>> httpd.conf settings:
>>
>> RewriteEngine on
>> <Proxy http://localhost:8080>
>>         Order deny,allow
>>         Allow from all
>> </Proxy>
>> <Location "/galaxy">
>>         Order deny,allow
>>         Allow from all
>>     # Take the $REMOTE_USER environment variable and set it as a header
>> in the proxy request.
>>         RewriteCond %{IS_SUBREQ} ^false$
>>         RewriteCond %{LA-U:REMOTE_USER} (.+)
>>         RewriteRule . - [E=RU:%1]
>>         RequestHeader set REMOTE_USER %{RU}e
>>         RequestHeader set X-URL-SCHEME https
>>         RewriteRule ^/galaxy$ /galaxy/ [R]
>>         RewriteRule ^/galaxy/(.*) http://localhost:8080/$1 [P]
>>         # Compress all uncompressed content.
>>         SetOutputFilter DEFLATE
>>         SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-vary
>>         SetEnvIfNoCase Request_URI \.(?:t?gz|zip|bz2)$ no-gzip dont-vary
>> </Location>
>>
>>
>>
>>
>> Thanks,
>>
>>
>>
>> ___________________________________________________________
>> The Galaxy User list should be used for the discussion of
>> Galaxy analysis and other features on the public server
>> at usegalaxy.org.  Please keep all replies on the list by
>> using "reply all" in your mail client.  For discussion of
>> local Galaxy instances and the Galaxy source code, please
>> use the Galaxy Development list:
>>
>>    http://lists.bx.psu.edu/listinfo/galaxy-dev
>>
>> To manage your subscriptions to this and other Galaxy lists,
>> please use the interface at:
>>
>>    http://lists.bx.psu.edu/
>