Hi all, sorry to bother you with this, but maybe someone's listening and willing to help me:
I've emerge Apache2 and Tomcat, and added mod_jk2 as described at http://www.dcdan.com/roller/page/dan/20031110 et al. Then I've added a file 80_mod_jk2.conf to /etc/apaches/conf/modules.d which simply loads the module if JK2 had been defined during startup. It all works pretty much perfect until here. The module gets loaded, JK2 connectors are set up and Tomcat processes *.jsp files which were forwarded by Apache like this: <IfModule mod_jk2.c> <Location "/*.jsp"> JkUriSet worker ajp13:localhost:8009 </Location> </IfModule> However, there's a folder "pictures" that I would like Apache to protect it with a password and share it via WebDAV. This it what's in the conf file for it: Alias /webdav /var/www/domain.com/htdocs/pictures <Location "/webdav"> Options None DAV On AuthName 'WebDAV' AuthType Basic AuthUserFile /var/www/domain.com/.htpasswd AuthGroupFile /dev/null <Limit GET OPTIONS> Require valid-user </Limit> </Location> Accessing it with WebDAV works as expected, but accessing it using a browser will give me an error message from TOMCAT saying that the ressource isn't available. How come that Tomcat deals with this request anyway, since the URI doesn't contain .jsp? The same error message occurs, when I just remove the JkUriSet statement. So it looks as if JK2/Tomcat will handle requests by itself as soon as it's loaded. Could anybody give me a hint on what's going on here? Best regards, - Christian -- Christian Aust mailto:[EMAIL PROTECTED] icq: 84500990 - Yahoo!: datenimperator - MSN: datenimperator PGP: A94E 0181 664D 27E3 F05A A751 6A7E 90D1 A0A3 DEC7 For those with an eye for the finer details, we salute you. - FGTH, Welcome to the pleasuredome -- [EMAIL PROTECTED] mailing list
