hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37939] - Decouple control logic (expect-continue handshake, etc) from HttpClientConnection
Date Sun, 18 Dec 2005 13:27:59 GMT
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=37939>.
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=37939





------- Additional Comments From olegk@apache.org  2005-12-18 14:27 -------
Created an attachment (id=17238)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=17238&action=view)
Patch (HEAD method handling)

Roland,
I looked at various options to solve the HEAD method problem. At the moment I
see only one alternative to passing the method name (or a reference to the
original request object) as a parameter to the
HttpClientConnection#receiveResponse(). All I can think of is post-processing
HEAD method responses with a response interceptor in the HTTP request executor.
The drawback of this solution is the that
HttpClientConnection#receiveResponse() per default will always generate an
HttpEntity instance for HEAD requests, even though this clearly does not make
sense. Please review the patch and let me know what you think

Oleg

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org


Mime
View raw message