-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hassan,
On 11/18/2009 2:09 PM, Hassan Schroeder wrote: > On Wed, Nov 18, 2009 at 10:59 AM, Jeffrey Trimble <jtrim...@cc.ysu.edu> wrote: > >> As you can see I'd like to do TWO things here: > > So if you have a different IP being used for Tomcat, you don't need > Apache httpd at all, AFAICT. > >> 1. Remove the port issue if possible--makes it simpler on users and >> shorter too. > > Configure the Tomcat Connector to use port 80 and listen on your > specified IP. Assuming Jeffrey doesn't want to run Tomcat as root, here are some suggestions: http://wiki.apache.org/tomcat/HowTo#How_to_run_Tomcat_without_root_priviledges.3F After re-reading that section, I take back my recommendation: it has little to no useful information. Instead, see this section instead: http://wiki.apache.org/tomcat/FAQ/Security#Q7 Using jsvc is the preferred way to bind to port 80 on *NIX. >> 2. Redirect http://digitial.maag.ysu.edu to digital.maag.ysu.edu/jspui >> interface and keep the other interfaces. > > Rename the /jspui Context to ROOT. Specifically, re-name your WAR file from jspui.war to ROOT.war (capitalization is critical). If you are using directory-based deployment instead of WAR files, then just re-name the directory from jspui to ROOT (again, use caps). If you use file-based deployment via CATALINA_BASE/conf/[service]/[host]/jspui.xml then change the name of the xml file from jspui.xml to ROOT.xml (caps!). If you are using server.xml to deploy your contexts, stop doing that (unless you're on TC 4.1 or 5.0, but you aren't using those very old versions, now are you?). Note that you may also have to re-wire some of your relationships in the other code that may check for referers [sic], or redirect back to the "home" webapp. You can do this with Apache httpd configuration using mod_alias's RedirectMatch directive like this: RedirectMatch permanent /jspui($|/.*) http://your-site/$1 If you are going to scrap Apache httpd and use only Tomcat, you can use this library to do some of your dirty work in a similar way: http://tuckey.org/urlrewrite/ Your best bet is to use this library in a new webapp that is deployed into /jspui and simply redirects everything similar to how I've done it above. Honestly, it would be better to re-configure your webapps to know about the new URL mapping, but it might be helpful to catch things that have fallen through the cracks, or to help-out users who have bookmarks or links pointing to your old URLs. Good luck, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksETfkACgkQ9CaO5/Lv0PAe0gCePIHwBJpj+3Oe95NiYq86vZLn PTMAn0ltGClaB/Sovid4w/+jaJy3P4wA =ejXW -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
