https://issues.apache.org/bugzilla/show_bug.cgi?id=56917
--- Comment #3 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to Ajay Sindwani from comment #2) > Both the servlet spec and Tomcat need to be updated then. Tomcat doesn't > have to wait for the servlet spec, unless the update is already accepted. Tomcat, being spec-compliant, must maintain spec-compliance. There are certainly examples of out-of-spec behavior in Tomcat which are usually controllable via certain configuration options. It seems like this could be one of them. Patches are always welcome. > The expense of doing 302 rewriting can be cleaned from numerous webserver > environments. Are you sure? If not all clients support it, then you can't remove that capability. It's one of the awful things about the web: you can't force users to upgrade. ;) -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
