A technician at Vivio alerted me to a cause of a few problems with regards to how the uriworkermap.properties file is set up. Specifically, the entry for the simple "/":
/=ajp13
The purpose of this mapping was to assist with enabling the default document, but it has ended up causing more problems then it solved. In IIS6/7 this mapping would work great if your default document needed to be passed off to Tomcat, but if your default document doesn't need to be passed, then this mapping gets in the way because it bypasses the built-in default document features of IIS. The connector simply examines the request, sees that the request matches a URI pattern, and passes it off to Tomcat. Tomcat then processes the request based on it's own default document parameters. This is NOT useful for sites that need, for example, ASP support.
I've performed tests in the following OS's with this mapping removed:
Windows 7 Professional (IIS7)
Windows 2008 R2 (IIS7)
Windows 2003 64-bit (IIS6)
In all cases, IIS is able to process default documents like it should. If the default document is a CFM file, then the request is passed off to tomcat based on the CFML filter definition that the iis7connect.bat or iis6connect.bat add.
NOTE: The filter does NOT establish filters for .jsp and other potentially useful extensions. It simply covers .cfm. If other extensions need to be added, a filter similar to the CFML one need to be added.
So... in an effort to reduce problems with this installer, we will be removing this mapping from future releases.
A technician at Vivio alerted me to a cause of a few problems with regards to how the uriworkermap.properties file is set up. Specifically, the entry for the simple "/":
/=ajp13
The purpose of this mapping was to assist with enabling the default document, but it has ended up causing more problems then it solved. In IIS6/7 this mapping would work great if your default document needed to be passed off to Tomcat, but if your default document doesn't need to be passed, then this mapping gets in the way because it bypasses the built-in default document features of IIS. The connector simply examines the request, sees that the request matches a URI pattern, and passes it off to Tomcat. Tomcat then processes the request based on it's own default document parameters. This is NOT useful for sites that need, for example, ASP support.
I've performed tests in the following OS's with this mapping removed:
Windows 7 Professional (IIS7) Windows 2008 R2 (IIS7) Windows 2003 64-bit (IIS6)
In all cases, IIS is able to process default documents like it should. If the default document is a CFM file, then the request is passed off to tomcat based on the CFML filter definition that the iis7connect.bat or iis6connect.bat add.
NOTE: The filter does NOT establish filters for .jsp and other potentially useful extensions. It simply covers .cfm. If other extensions need to be added, a filter similar to the CFML one need to be added.
So... in an effort to reduce problems with this installer, we will be removing this mapping from future releases.
-Jordan