Markus, Is the header name called "Authentication" ? If so, we had this exact same issue a few years ago. The length of this HTTP header was too long for mod_jk to process and the request was getting dropped. I think you might be able to configure the packet size of mod_jk now to get around this problem.
Our solution a few years ago was I built an ISAPI filter that removed the Authentication header before it was sent to Tomcat (since this wasn't needed). Scott On Fri, Apr 17, 2009 at 10:46 AM, baumar <mbj...@active.ch> wrote: > > Hi, > > We are running an application on Tomcat 6. The authorization is down by IIS > with Integrated Windows authentication selected. > > Whenever we try to access any page (with IE6), we get a "request entity too > large" response. > > We switched IIS to Basic authentication, then it works. By analyzing the > network traffic, we saw that IIS is adding a kerberos header with encrypted > data and guess this data cannot be handled by the jconnector or tomcat. we > made a test where we switched off tomcat and still got the same error, so > unless we didn't get some cached reply, this means the error might be > thrown > by the jconnector, but we have no clear evidence. > > Did anybody encounter a similar case or know how to resolve this? > > Thanks > > Markus > > > -- > View this message in context: > http://www.nabble.com/%22Request-entity-too-large%22-when-using-SSO-%28IIS-Integrated-Windows-authentication--Tomcat-%29-tp23099072p23099072.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
