trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Carroll <solidwallofc...@oath.com>
Subject Re: Change in shn response (logging)
Date Mon, 14 Jan 2019 19:50:57 GMT
One of the issues with this is what exactly was the difference between
`pqsn` and `shn`? Did they different when using parent.config?

On Fri, Jan 11, 2019 at 11:54 AM Steve Malenfant <smalenfant@gmail.com>
wrote:

> Was doing some testing this morning and noticed that I couldn't find my
> traffic by the origin server hostname anymore using our logging system.
> While discussing with a few folks, looks like the "shn" field isn't
> reporting the origin server hostname under certain circumstances, for
> example when used with parent.config.
>
> shn now reports the IP address or hostname used in the parent.config,
> which is what we used pqsn/pqsi field before.
>
> In the pull request https://github.com/apache/trafficserver/pull/3860,
> there is a workaround using the client/server host header that can be used.
> That header contains also a port.
>
> I know we applied the logic of pqsn to shn, but pqsn had a different
> meaning than origin server hostname.
>
> pqsnThe proxy request server name; the name of the server that fulfilled
> the request.
>
> The PR says that the psqn logic was proper, although I don't think it was
> the case for the definition of shn.
>
> shnThe hostname of the origin server.
>
> Few things could happen.
> - Revert back the change
> - Adjust my logging system (and everybody else maybe)
>
> Any explanation that the 5.x/6.x behavior was causing?
>
> Thanks,
>
> Steve
>


-- 
*Beware the fisherman who's casting out his line in to a dried up riverbed.*
*Oh don't try to tell him 'cause he won't believe. Throw some bread to the
ducks instead.*
*It's easier that way. *- Genesis : Duke : VI 25-28

Mime
View raw message