You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2014/08/23 03:34:33 UTC
[Bug 56884] New: Support for HTTP Method PATCH under the AJP
protocol
https://issues.apache.org/bugzilla/show_bug.cgi?id=56884
Bug ID: 56884
Summary: Support for HTTP Method PATCH under the AJP protocol
Product: Tomcat Connectors
Version: unspecified
Hardware: PC
Status: NEW
Severity: enhancement
Priority: P2
Component: isapi
Assignee: dev@tomcat.apache.org
Reporter: jasonreichle@gmail.com
AJP protocol currently does not support the HTTP method PATCH.
http://tools.ietf.org/html/rfc5789
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 56884] Support for HTTP Method PATCH under the AJP protocol
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56884
Jason <ja...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Jason <ja...@gmail.com> ---
Thanks Konstantin, I indeed did discover that there was no real problem
specifically with the tomcat connecter, Better documentation would be
appreciated.
Javas default HttpUrlConnectionClient client was the culprit, which is
unrelated to this project. A series of poor logging resulted in the original
request.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 56884] Support for HTTP Method PATCH under the AJP protocol
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56884
Konstantin Kolinko <kn...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #1 from Konstantin Kolinko <kn...@gmail.com> ---
The protocol [1] does support arbitrary methods.
See Java side source code at [2][3].
Search for "request.method()" in [2].
Arbitrary methods are transmitted in the following way:
1. The method name code is Constants.SC_M_JK_STORED = 0xFF
The code is missing from codes list in "method" section [11], though.
(FIXME: Add "0xFF" to the list of methods in [11] ?)
2. There will be request attribute with code Constants.SC_A_STORED_METHOD = 13.
It is documented as "stored_method 0x0D" in "Attributes" section [12],
but no explanation is given beyond that.
(FIXME: Add a comment on what "stored_method" attribute is for in [12]?)
So, is there any real problem, or you are just asking for a more effective
representation? I think that there is no real need for that.
I am leaving this open, to consider updating the documentation on the protocol.
[1] http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html
[11] http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html#method
[12] http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html#Attributes
[2]
http://svn.apache.org/viewvc/tomcat/tc8.0.x/tags/TOMCAT_8_0_11/java/org/apache/coyote/ajp/AbstractAjpProcessor.java?view=markup
[3]
http://svn.apache.org/viewvc/tomcat/tc8.0.x/tags/TOMCAT_8_0_11/java/org/apache/coyote/ajp/Constants.java?view=markup
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org