https://issues.apache.org/bugzilla/show_bug.cgi?id=55595
--- Comment #5 from Chuck Caldarale <chuck.caldar...@unisys.com> --- (In reply to Brian Tajuddin from comment #4) > Wrapping the request seems reasonable on the surface, but it forces the > application to assume that the data structures underneath the parameters > cannot be changed by the container without going through one of the > getParameter...() methods. Is this an assumption that can be safely made? I think you're missing the point: _none_ of the APIs exposed by HttpServletRequest are thread-safe, regardless of how innocuous they might seem. It's up to the application to insure that only one thread at a time utilizes the HttpServletRequest object. (The same applies to the response object.) Having a filter wrap the request and response with your own objects that synchronize internally is the way to go. -- 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
