So I looked into it some more and noticed the <error-page> definitions
depend on a sym-linked dir in each webapp doc root and those are not being
followed either.

So it seems that this host definition:

      <Host name="site1.company.com" debug="0" appBase="/www/site1/webapps"
       unpackWARs="true" autoDeploy="true">

        <!-- activate JK for this host -->
        <Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
                  append="true"
                  forwardAll="false"
                  modJk="/usr/local/apache2/modules/mod_jk.so" />

        <Valve className="org.apache.catalina.authenticator.SingleSignOn"
                   debug="0"/>

        <Logger className="org.apache.catalina.logger.FileLogger"
                 directory="logs"  prefix="localhost_log." suffix=".txt"
                timestamp="true"/>

          <DefaultContext>
            <!-- set up virtual host variable  -->
            <Parameter name="siteRole" value="site1"/>
            <!-- Allow Tomcat to follow sym-links -->
            <Resources
className="org.apache.naming.resources.FileDirContext"
               allowLinking="true"/>
          </DefaultContext>
          <!-- set up document context to secure static files served by
Tomcat -->
          <Context path="" docBase="/www/site1">
            <Resources
className="org.apache.naming.resources.FileDirContext"
               allowLinking="true"/>
          </Context>
      </Host>

does not include setting allowLinking for the apps within it.  How do I do
allowLinking without having to explicitly define every app context in the
server.xml (thus defeating the purpose of deployment descriptors)?


> -----Original Message-----
> From: Madere, Colin 
> Sent: Thursday, March 20, 2003 6:01 PM
> To:   'Tomcat Users List'
> Subject:      TC 4.1.18 allowLinking not working for form-based login
> 
> So allowLinking works fine for me except when the form-based auth part of
> Tomcat kicks in.  If the file I set as my login-form is a sym-linked file,
> I get a 404.  Change that file to a real file and it works.
> 
> I tried on a fresh Tomcat 4.1.18 setting the allowLinking resource on the
> ROOT context, but this didn't work for my autodeplyed test app.
> 
> So is there a way to set allowLinking for the auth module (wherever that
> may be found)?
> How about for auto-deployed webapps dropped in the Tomcat default webapps
> folder (don't need this, but I'm curious how this is done since it would
> be similar to solving the above problem)?
> 
> If no one has an answer, how about a pointer into the code where the auth
> module looks for the login form?
> 
> Thanks in advance.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to