You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by bu...@apache.org on 2004/07/18 21:24:52 UTC
DO NOT REPLY [Bug 25468] -
Provide HttpParser plug-in mechanism
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=25468>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=25468
Provide HttpParser plug-in mechanism
------- Additional Comments From ck@rrzn.uni-hannover.de 2004-07-18 19:24 -------
This bug has been left open for a while, so I decided to re-check the
need/interest for having a pluggable HttpParser instead of the current static
implementation.
An updated patch is attached including a "DefaultHttpParser" (copy of the
previous HttpParser) and, as an exemplary alternative, a "PickyHttpParser",
which now includes Eric's suggestions on the limit values, a total header
section limit and a per-method configuration (using custom PickyHttpParser
instances).
There is a testcase (TestPickyHttpParser) demonstrating three cases where the
default HttpParser would fail.
For compatibility, I marked the old, static HttpParser class as being
"deprecated" ;it simply redirects calls to the new DefaultHttpParser.
Please let me know what you think :)
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org