Re: [Unbearable] sec-token-binding header in the wild

I see the sec-token-binding header for both www.google.com and
www.chromium.org from chrome on os x (version 56.0.2924.87).

On Wed, Feb 15, 2017 at 3:29 PM, John Bradley <ve7jtb@ve7jtb.com> wrote:

> Strange I see them on both sites with Edge.
>
> With chrome on osx and windows I am not seeing them after turning on the
> flag and restarting.
>
> I don’t know if the header capture is messing with it somehow.
>
> Google.cl negotiated TB with Edge.
>
> John B.
>
> > On Feb 15, 2017, at 6:12 PM, =JeffH <Jeff.Hodges@KingsMountain.com>
> wrote:
> >
> > fyi/fwiw...
> >
> > target: https://www.chromium.org/
> >
> > sec-token-binding:AIkAAgBBQMaFRvLPy1uUBZer64ZluK
> 8oBJ8kpcnO84kmCX29demwilh57_4gqlqRLBcZ_dh8x9KdN6TQQZWciZlGmhZp3sUAQFW
> hQBmwYSLGqlQ59KCOsYpn7Ex1dB_L5bAUTdEjd98Y5CY7NY6aczxi2gC7I
> 6xEMAC4tONGdNOjoALTLt72REUAAA
> >
> > I used the built-in chrome developer tools to examine the request
> headers and obtain the above STB
> >
> >
> > [ innarestingly enuff, if one targets https://www.google.com/, it seems
> developer tools only displays the below...
> >
> > Provisional headers are shown
> > Referer:https://www.google.com/
> > User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
> > ]
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Unbearable mailing list
> > Unbearable@ietf.org
> > https://www.ietf.org/mailman/listinfo/unbearable
>
>
> _______________________________________________
> Unbearable mailing list
> Unbearable@ietf.org
> https://www.ietf.org/mailman/listinfo/unbearable
>
>