https://issues.apache.org/bugzilla/show_bug.cgi?id=47714
--- Comment #19 from Kevin J Walters <k...@ms.com> --- My general conclusion in this area is anything that's effectively doing rpc should be using some sort of id to match requests and responses and allow the client to discard/warn/retry on mismatches. This feature can be found in sun rpc from 1988 and probably earlier implementations, it's not a new concept. This type of bug where the the wrong response ends up with the client and in this case often the web browser can be extremely hazardous. It's a worryingly common bug on connection based transports, pools of connections and multi-threaded clients. -- 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
