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, usability
Fixing a Mac OSX Leopard Login Loop Caused by Launch Services:
Is OCLC's Change of WorldCat Record Use/Transfer Policy Related to the Google Book Search Agreement?:
Google Book Search Settlement: Introduction, Public Announcements:
"Draft Principles for Digitized Content" from the Digitization Policy Task Force of ALA's Office for Information Technology Policy:
George Mason University Sued by Thomson Reuters over Zotero: