Dear Tomcat-users, I'm working with Jakarta-Tomcat for a while, and I'd like to post some questions regarding problems I ran into: 1. At what level should I install the jakarta-filter? In the IIS Management Console, it is possible to install filters on the level of a single website or the webserver. While using Allaire's JRun on the same machine, I noticed that JRun installs a filter as well on the level of the webserver. To make sure requests for JSP-pages and servlets reach the Tomcat servlet-runner (in order not to be handled by JRun), it seems to be necessary to install the Jakarta-Tomcat filter on the level of the webserver as well, with a higher priority than the JRun-filter. Does anyone have any experience with this? 2. Installing and above all LOADING a filter seems to be a delicate undertaking. Sometimes it works (green arrow), most of the time it doesn't (red arrow)! On some machines, the filter starts immediately on the webserver-level, on others on the level of the website. I always follow the guidelines in the Tomcat IIS HowTo document (by now, I know them out of my head ;-). Does anyone know why a filter does or does not start on one machine and not on the other? 3. Once the filter is installed and loaded, I'd like to make use of it. When running the filter, all the contexts mounted to the ajp12 worker should be recognized and handled by the Tomcat servlet runner, without using the 8080-port number. Now, on some machines, the filter is installed well, the contexts are added to the file "uriworkermap.properties", and still, I have to add the port 8080 to my webserver-hostname. What am I overlooking? 4. CaSe SeNsiTiViTy? Why is Tomcat so sensitive for the difference between lower- and uppercase? I just lost some precious time trying to use a taglib which could not be found. I seemed to be the path "/web-inf/" in the file "web.xml" that should have been in uppercase, thus "/WEB-INF/". The same kind of problem occurs when trying to call JSP-pages with path-names that are in the wrong case. What are the developers going to do about this sensitive behavior? Thanks to everyone for taking the time to answer or comment one of my questions. Best regards, Joeri Theelen
