Orsburn (Static Content)

Apache httpd seems to have an issue that flusters the configuration file parser when a series of backslashes are present in a comment. The following snippet is taken from a vhosts configuration file.  Notice the 5 backslashes at the end of the first line.  # ///// Be sure to manage the corresponding [wrap]         directory block in                  [wrap]         httpd-directories.conf \\\\\ <VirtualHost *:80>     ServerAdmin webmaster@domain.tld     ServerName server.domain.tld     DocumentRoot "/path/to/server.domain.tld"     ErrorLog "/path/to/server.domain.tld-error.log"     CustomLog "/path/to/server.domain.tld-access.log" common </VirtualHost> With these backslashes present, an attempt to start the server wil...

By default Apache Tomcat does not come configured to handle the path_info server variable information commonly found in SES (search engine safe) compatible URLs.  An SES URL might look like:  www.domain.tld/index.cfm/user/123 .  Combining Tomcat as the servlet container with other technologies like Railo and Mura , this missing feature can become problematic and frustrating (redundancy provided for emphasis). A scenario The path_info data is traditionally available to CFML applications a la the CGI.path_info variable.  Applications often refer to this variable to resolve URLs to specific actions or details of the application.  One such example is Mura.  The CMS (content management system) has the ability to host several sites from a single instance of the application.  While most sites are likely set up to be accessed from their own domain names, in some cases, the sites will be accessed through an identifier in the URL.  For example, as...