Fronting Tomcat with Apache HTTPD to Remove Ports and Context Paths
In this How-To guide, I show a combination of software and configuration to clean up URLs by removing the port numbers of the Java servlet engine (Tomcat) and the context path of the application. The goal is to create “cool URLs” that are are short (removing the unnecessary context path) and follow conventions (using the default port “80″ rather than “8080″). OhioLINK also uses a custom access control module — built for Apache HTTPD — which makes the fronting of Apache HTTPD for Tomcat even more desirable.
Also tagged apache, howto, httpd, usability, web development
![[Creative Commons Logo]](/wp-content/themes/local/cc-by-na-sa-30-us-88x31.png){kind=small}
This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/us/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA.
Using Twitter For Service Outage Awareness:
Riding the Waves of Content and Change:
The Complex World of the Textbook:
PocketModMac: MacOSX PocketMod Generator Via Print Dialog:
Amazon Catalog Updates:
Clay Shirky on the Need for Better Information Filters:
Fixing a Mac OSX Leopard Login Loop Caused by Launch Services: