2013/2/12 Brad McEvoy <b...@fuselms.com>: > On 12/02/13 09:53, Mark Thomas wrote: >>> >>> >Can anyone suggest a way to >>> >disable this "feature" short of hacking tomcat? >> >> You don't want to disable sending 100 Continue responses. >> >> Ideally, you want to delay when it is sent until after any >> authentication (so the 401 goes back to the client before they send the >> body). >> >> I'm not sure how feasible that would be. >> >> Is your servlet generating the 401? It it was a standard authenticator >> generating the 401 it might be doable. If it is a user servlet then that >> is going to be trickier. It doesn't help that the Servlet API has no >> mechanism for sending a 101. > > The milton servlet handles the acknowledgement cycle, including > authorisation checks and 401 response if needed. > > All thats needed is a container wide parameter to simply ignore Expect > headers. I'd be happy to poke around in tomcat's innards and perhaps submit > a patch. Would this be in the Http11Processor?
Certainly not. Have you read the source code, or only that old thread? The processor is The method that sends acknowledgment is o.a.catalina.connector.Response.sendAcknowledgement(). 1) Acknowledgment happens is StandardContextValve or in FormAuthenticator. 2) Looking at stacktraces in Bugzilla reports, authentication happens before StandardContextValve is involved. Doesn't it already works for you? How your authentication is configured? 3) It probably would not work if Tomcat is behind HTTPD, as AJP processors do not have this feature (ActionCode.ACK). > > Yep, sadly the servlet API seems to have completely overlooked this and so > everyone has to figure out their own way of dealing with it > Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
