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

ASF GitHub Bot commented on TS-4012:
------------------------------------

GitHub user ericcarlschwartz opened a pull request:

    https://github.com/apache/trafficserver/pull/336

    [TS-4012] tcp_reused log field doesn't work for http2/spdy

    JIRA: https://issues.apache.org/jira/browse/TS-4012

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ericcarlschwartz/trafficserver ts-4012

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/336.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #336
    
----
commit b2304952f701379e37efd6135c904e34876be95e
Author: ericcarlschwartz <eschwartz1...@gmail.com>
Date:   2015-11-13T22:59:11Z

    [TS-4012] tcp_reused log field doesn't work for http2/spdy

----


> tcp_reused log field doesn't work for http2/spdy
> ------------------------------------------------
>
>                 Key: TS-4012
>                 URL: https://issues.apache.org/jira/browse/TS-4012
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Eric Schwartz
>            Assignee: Eric Schwartz
>             Fix For: 6.1.0
>
>
> This is something we noticed at Yahoo!
> Because it uses the HttpClientSession transact_count, the tcp_reused log 
> field will not properly work for http2 and spdy, where the HttpClientSession 
> isn't reused. 
> We need to essentially count the number of initiated streams instead.
> We've got a fix that does this for HTTP2. With SPDY eventually dying off, 
> does it make sense to also submit a change to fix this for SPDY? We have code 
> to do this as well, but it currently involves an H2 dependency that might be 
> undesirable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to