Ok, so defining my app as the ROOT one is definitely not an option.Now I'm sorry to ask but could you be a little more specific about where I need to add those mod_rewrite configuration bits? Because I'm not really an Apache configuration wizard and mod_rewrite is especially scary to me.
2008/6/22 Rainer Jung <[EMAIL PROTECTED]>: > Hi Sebastien, > > Sebastien ARBOGAST schrieb: > > I've got my JBoss 4.2 server running and I managed to configure one >> virtual >> host with mod_jk to get to it without having to enter the 8080 port.Here >> is >> my VirtualHost configuration: >> >> >> <VirtualHost *:80> >> ServerAdmin [EMAIL PROTECTED] >> ServerName myserver.com >> >> JkMount /* loadbalancer >> >> ErrorLog /var/log/apache2/myserver-error.log >> # Possible values include: debug, info, notice, warn, error, crit, >> >> # alert, emerg. >> >> >> LogLevel warn >> CustomLog /var/log/apache2/myserver-access.log combined >> >> >> </VirtualHost> >> >> >> So no when I access the JIRA application installed on this server, I can >> do >> it either from http://myserver.com:8080/jira or from >> http://myserver.com/jira >> Now I would like to be able to skip the jira suffix and access this same >> application from http://myserver.com, but without making JIRA the home >> application on my JBoss server. >> >> >> Is that possible? How can I do that? >> > > Use mod_rewrite in Apache httpd and a configuration similar to: > > RewriteRule ^/(.*)$ /jira/$1 [PT] > > and > > JkMount /jira|* loadbalancer > > (JkMount /* would do it to, but is less precise). > > If you want mod_jk to act after an internal rewrite, you need to use the > "PT" flag in the RewriteRule. > > If it doesn't work, add a RewriteLog and see, what your RewriteRules are > actually doing. > > A totally different approach would be, to deploy the jira webapp as the > so-called ROOT context in Tomcat. Then it would be reachable via > http://myserver.com:8080/ and thus also via http://myserver.com/ by the > same JkMount /*. Although all applications should be freely eployable under > any context name, not all are actually. So you would need to experiment, if > you can deploy jira as ROOT webapp. Using the ROOT webapp for normal > production is not recommendable in general, because if you always deploy > your webapps as ROOT, you will no longer be able to share a Tomcat instance > for multiple webapps (at least not in the same host), and secondly the ROOT > context catches all requests, that do not map to any other webapp, so is > generally also a good indicator if something is going wrong. > > Have fun, > > Rainer > > --------------------------------------------------------------------- > 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
