https://issues.apache.org/bugzilla/show_bug.cgi?id=56831
--- Comment #4 from Mark Thomas <ma...@apache.org> --- That you only see this bug on Tomcat could mean that Tomcat is following a strict interpretation of the spec whereas other containers are being more lenient. Given that you know the application far better than the Tomcat developers, it makies things a lot simpler if the bug is presented in the form: - the attached app calls method X with parameters Y - as per the Servlet/JSP/EL/WebSocket/HTTP/etc. spec, Tomcat should return A but instead returns B rather than the Tomcat developers having to dig their way through an app they have no knowledge of to try and work out which API call (that might be returning a completely valid result) is causing the problem. It isn't that we aren't going to look into this bug - I'm going to start on it now - but you could really help move things along by providing a more specific bug report than "The attached app throws an expception when I do this." -- 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
