It's a trust issue. By default, 3.3 doesn't trust IIS's/Apache's authentication and will check it again.
I agree that we should implement tomcatAuth in 4.0.3 if at all. ----- Original Message ----- From: "Kevin Seguin" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Thursday, February 14, 2002 6:18 PM Subject: RE: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4 Ajp13Request.java > > > > > De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > > Enviado el: viernes 15 de febrero de 2002 1:55 > > > > Perhaps is better to have explicit control over that, to disable or > > enable the control of the native auth honoring..the infamous > > tomcatAuthentication attribute.. > > I don't quite understand, as the patch only add filtering out an empty > string, right ? > Or did I miss something ? > > In any case, I just applied the patch as it looked ok to me. > If the patch is > bad, revert it. > i think native auth honoring is different than the problem this patch addresses. i don't think the patch should be reverted (so long as it works :)). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
