On 08/05/18 17:59, Christopher Schultz wrote: <snip/> > This bites enough people that it may be worth correcting, or at least > changing the behavior when it happens. > > AJP already encodes the packet-size in the header of each packet. Why > not simply compare that to the MaxPacketSize on the Tomcat side and > issue a useful error message instead of whatever is currently happening?
Done. Most likely there would have been an error message logged anyway, but that would have been about the next bytes being an invalid packet header. Now there is an explicit error logged for the message being too big. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
