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

ASF GitHub Bot commented on HTTPCLIENT-1806:
--------------------------------------------

Github user Coderec commented on the issue:

    https://github.com/apache/httpcore/pull/36
  
    It's said that travis-ci build failed. 
    
    However, my code has nothing to do with the test, which is like this: 
`Tests in error: Http2IntegrationTest.testSlowResponseProducer:506 » Execution 
org.apache.hc.co...`
    
    And, I could run the tests successfully on my Mac.
    
    Is this an error of travis-ci itself?


> Add a route inteceptor
> ----------------------
>
>                 Key: HTTPCLIENT-1806
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1806
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpClient (async), HttpClient (classic)
>            Reporter: Baosen Cui
>            Priority: Minor
>             Fix For: 5.0
>
>
> I had meet a problem that I need to log the time cost by  method 
> “establishRoute”( in httpclient ).
> Since there seems nothing to support, I wrote a interceptor into HttpCore 
> coping the structure of “HttpProcessor"
> Would this be accepted? Or there has already something alike?
> @ThreadSafe // provided injected dependencies are immutable
> public final class ImmutableRouteProcessor implements RouteProcessor {
> ...
> }
> public interface PostRouteInterceptor {
>   void postProcess(final HttpRequest request, final HttpContext context);
> }
> public interface PreRouteInterceptor {
>   void preProcess(final HttpRequest request, final HttpContext context);
> }
> public interface RouteProcessor extends PreRouteInterceptor, 
> PostRouteInterceptor {
> }



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to