My purpose was to hide two things:- the 8080 port in the URL, not only for cosmetic reasons but also to prevent issues with my corporate firewall blocking everything but 80 - the fact that my application runs under /jira application context by using a subdomain like they do it on bugs.adobe.com for example... but I just realized that they also have jira in the URL at the end so I guess it's too hard to be worth it.
Thanks a lot to you guys. Sebastien 2008/6/22 Rainer Jung <[EMAIL PROTECTED]>: > Sebastien ARBOGAST schrieb: > >> Thanks a lot. Now it works great. >> One last thing though: when the page is displayed, the end URL is still >> http://bugs.epseelon.org/jira >> Is there a way not to show the redirected URL ? >> > > The redirect comes from the JBoss behind the Apache. > > Getting rid of those could be done via mod_proxy instead of mod_jk. But > before, you should check, if Jira actually supports running under a reverse > proxy, that changes the URL prefix. > > At least this > > > http://jira.atlassian.com/browse/JRA-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > seems to indicate, that Jira will produce links which contain the context > path, so the outside world will always know: > > "JIRA always references absolute URLs, including the context path (the path > at which you deployed JIRA)." > > I don't know though, if this is still up to date. > > I never tried it, but maybe something like the following could do the same > trick as mod_proxy with ProxyPassReverse: > > Load module mod_headers > > Add to your VirtualHost (one long line): > > Header always edit Location http://myserver.com/jira/ http://myserver.com/ > > Then test with a commandline browser like curl, what you get for > > curl -v -D - http://myserver.com/ > > If it doesn't work you could try > > Header always edit Location http://myserver.com/jira/(.*) > http://myserver.com/$1 > > which should be equivalent, but that's not 100% clear from the docs. > > If your original aim was only making Jira available under > http://my.server.com/, and you don't care much about the followup URLs > (that's what most people want), then you don't need mod_rewrite: > > RedirectMatch permanent ^/$ http://myserver.com/jira/ > > (which is implemented in mod_alias). > > Regards, > > Rainer > > 2008/6/22 David Smith <[EMAIL PROTECTED]>: >> >> This added before your RewriteRule prevents requests to /jira/* from >>> being >>> handled by the rewrite rule. This should break the endless redirect: >>> >>> RewriteCond %{REQUEST_URI} !^/jira/.* >>> >>> --David >>> >>> >>> Sebastien ARBOGAST wrote: >>> >>> Thanks a lot for these precisions. I already had mod_rewrite loaded but >>>> when >>>> I configured my VirtualHost like the following, I got a redirect loop >>>> error: >>>> <VirtualHost *:80> >>>> ServerAdmin [EMAIL PROTECTED] >>>> ServerName bugs.epseelon.org >>>> >>>> RewriteEngine On >>>> RewriteRule ^/(.*)$ /jira/$1 [PT] >>>> RewriteLog /var/log/apache2/rewrite.log >>>> RewriteLogLevel 9 >>>> >>>> JkMount /* loadbalancer >>>> >>>> ErrorLog /var/log/apache2/jira-error.log >>>> # Possible values include: debug, info, notice, warn, error, crit, >>>> >>>> # alert, emerg. >>>> >>>> LogLevel warn >>>> CustomLog /var/log/apache2/jira-access.log combined >>>> >>>> </VirtualHost> >>>> >>>> Here is the full log in rewrite.log: >>>> >>> > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Sébastien Arbogast http://sebastien-arbogast.com
