[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342058#comment-16342058
 ] 

ASF subversion and git services commented on HTTPCLIENT-1900:
-------------------------------------------------------------

Commit 4eeeb27893b9ddd280984b8c9056580601061679 in httpcomponents-client's 
branch refs/heads/4.6.x from [~olegk]
[ https://git-wip-us.apache.org/repos/asf?p=httpcomponents-client.git;h=4eeeb27 
]

HTTPCLIENT-1900: proxy protocol processor does not post-process CONNECT 
response messages


> Add httpresponse interceptor processing on 'CONNECT' request 
> -------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1900
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1900
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (classic)
>            Reporter: Gael Stephant
>            Priority: Minor
>             Fix For: 4.5.6, 5.0 Beta2
>
>
> Hello 
> I have a use case, where i need to get a cookie received on a 'CONNECT' 
> request.
> In the method createTunnelToTarget of the class MainClientExec. Only 
> interceptors on request can be used.
> I wish to be able to process interceptors on the response.
> Something like that : 
>  
> {code:java}
> package org.apache.http.impl.execchain;
> public class MainClientExec implements ClientExecChain {
>     private boolean createTunnelToTarget(
> ...
>         this.requestExecutor.preProcess(connect, this.proxyHttpProcessor, 
> context);
>         while (response == null) {
> ...
>         }
>         // The processing code of response interceptors 
>         this.requestExecutor.postProcess(response, this.proxyHttpProcessor, 
> context);
> ...
>     }
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to