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, tomcat, web development



Google Book Search Settlement: Introduction, Public Announcements:
Google Book Search Settlement: Reviewing the Notice of Settlement:
Google Book Search Settlement: Public Access Service:
Preliminary Court Approval of Google Book Settlement; Final Approval Hearing Set:
Is OCLC's Change of WorldCat Record Use/Transfer Policy Related to the Google Book Search Agreement?: