Mark, On 2/4/21 8:52 AM, Mark Thomas wrote: > On 04/02/2021 13:28, Christopher Schultz wrote: >> I think this should be done in a Valve that is enabled by default, but >> can be disabled, rendering zero penalty for "well-behaved" applications. >> The Valve can simply wrap the response with a wrapper that either prints >> an error to the log (maybe first migration path, enabled now) or throws >> an exception (second migration path, in the future). > > Valves can't wrap requests or responses. It would require some major > refactoring to make that possible.
Well, you *can* wrap them. Maybe it's not a good idea[1], but its certainly possible. -chris [1] https://bz.apache.org/bugzilla/show_bug.cgi?id=45014 I still don't understand why wrapping the request is such a risky thing. Only in Tomcat code, suddenly OOP decoration pattern doesn't apply? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
