I think this is a bug. I just created a PR to fix it - https://github.com/apache/trafficserver/pull/4407
Also for one of your examples, you are missing an empty space at the end. So instead of this, bin/traffic_via "uScHs f p eN:t cCHp s" it should be bin/traffic_via "uScHs f p eN:t cCHp s " Of course it still wouldn't work unless with the fix. Thanks. Kit On Fri, Oct 12, 2018 at 6:33 AM Jin <j...@tower-research.com> wrote: > > curl with -v reports: > > ... > < Via: http/1.1 cache02.company.com (ApacheTrafficServer/8.0.0 [uScHs f p > eN:t cCHp s ]) > ... > or > < Via: http/1.1 cache02.company.com (ApacheTrafficServer/8.0.0 > [uScMsSfWpSeN:t cCMp sS]) > > > However, the same version of traffic_via failed to parse the via code > > $ bin/traffic_via "[uScMsSfWpSeN:t cCMp sS]" > Via header is [uScMsSfWpSeN:t cCMp sS], Length is 24 > > Invalid VIA header. VIA header length should be 6 or 23 characters > Valid via header format is > [u<client-stuff>c<cache-lookup-stuff>s<server-stuff>f<cache-fill-stuff>p<proxy-stuff>e<error-codes>:t<tunneling-info>c<cache > type><cache-lookup-result>p<parent-proxy-conn-info>s<server-conn-info>] > > $ bin/traffic_via "uScHs f p eN:t cCHp s" > Via header is uScHs f p eN:t cCHp s, Length is 21 > > Invalid VIA header. VIA header length should be 6 or 23 characters > Valid via header format is > [u<client-stuff>c<cache-lookup-stuff>s<server-stuff>f<cache-fill-stuff>p<proxy-stuff>e<error-codes>:t<tunneling-info>c<cache > type><cache-lookup-result>p<parent-proxy-conn-info>s<server-conn-info>] > > > Could this be a bug or something? > > Thank you. > > Jin. > > > > -- > Sent from: http://apache-traffic-server.24303.n7.nabble.com/
