You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/07/22 15:02:09 UTC
DO NOT REPLY [Bug 11040] New: -
Header field causes strange AJP Connector behaviour
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11040>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11040
Header field causes strange AJP Connector behaviour
Summary: Header field causes strange AJP Connector behaviour
Product: Apache httpd-1.3
Version: 1.3.23
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: core
AssignedTo: bugs@httpd.apache.org
ReportedBy: marcin.jackowski@comarch.pl
If in http headers there is field:
profile:not-supported-header
(i got this from WAP-gateway)
there's sth wrong with relaying request (espesially SUBMIT) to tomcat contener.
If in http headers there is field:
profile2:not-supported-header
(hand-made)
there's an error occuring in tomcat debug
java.lang.NumberFormatException
at org.apache.tomcat.util.buf.Ascii.parseInt(Ascii.java:188)
at org.apache.tomcat.util.buf.ByteChunk.getInt(ByteChunk.java:439)
at org.apache.tomcat.util.buf.MessageBytes.getInt(MessageBytes.java:577)
at org.apache.ajp.Ajp13.decodeRequest(Ajp13.java:393)
at org.apache.ajp.Ajp13.receiveNextRequest(Ajp13.java:309)
at org.apache.ajp.tomcat4.Ajp13Processor.process
(Ajp13Processor.java:339)
at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:424)
at java.lang.Thread.run(Thread.java:512)
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org