https://bz.apache.org/bugzilla/show_bug.cgi?id=66196

--- Comment #11 from gabriel.holl...@appian.com ---
Looking over the thread here, it sounded like the path forward was to log, and
potentially drop the header for Http1.1

However that same change wasnt done for the AJP Processor, causing invalid
headers to suddenly break upon tomcat upgrade (discover in our 8.5.x usage)

java.lang.IllegalArgumentException: The Unicode character [–] at code point
[8,211] cannot be encoded as it is outside the permitted range of 0 to 255
                at
org.apache.tomcat.util.buf.MessageBytes.toBytesSimple(MessageBytes.java:290)
                at
org.apache.tomcat.util.buf.MessageBytes.toBytes(MessageBytes.java:261)
                at
org.apache.coyote.ajp.AjpMessage.appendBytes(AjpMessage.java:172)
                at
org.apache.coyote.ajp.AjpProcessor.prepareResponse(AjpProcessor.java:1121)
                at
org.apache.coyote.ajp.AjpProcessor$SocketOutputBuffer.doWrite(AjpProcessor.java:1511)
                at org.apache.coyote.Response.doWrite(Response.java:602)
                at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:356)
                at
org.apache.catalina.connector.OutputBuffer.flushByteBuffer(OutputBuffer.java:846)
                at
org.apache.catalina.connector.OutputBuffer.realWriteChars(OutputBuffer.java:470)
                at
org.apache.catalina.connector.OutputBuffer.flushCharBuffer(OutputBuffer.java:851)
                at
org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:250)
                at
org.apache.catalina.connector.CoyoteWriter.close(CoyoteWriter.java:107)

Is there any chance the same handling for HTTP 1.1 could apply to AJP?

-- 
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

Reply via email to