How Verizon's Advertising Header Works
webpolicy.org
How Verizon's Advertising Header Works
1–10 of 68 posts
Re: How Verizon's Advertising Header Works
#2I haven't had the opportunity to tinker with this, but what if the client sends a X-UIDH: header of it's own? Will VZW overwrite the header, or will it pass it through? If it doesn't clobber it, there's a browser plugin waiting to be written.
Re: How Verizon's Advertising Header Works
#3Interesting - my cookie, collected the day this broke, has the same prefix as the author: "981596494\x00"
I'm now getting a different cookie (same physical location) that starts with: "379689122\x00"
Re: How Verizon's Advertising Header Works
#4Is this even legal? I mean are ISPs, or telecom in general allowed to identify the requester without their permission? But I imagine it will not work on encrypted connections. SSL FTW?!
Re: How Verizon's Advertising Header Works
#5I haven't had the opportunity to tinker with this, but what if the client sends a X-UIDH: header of it's own? Will VZW overwrite the header, or will it pass it through? If it doesn't clobber it, there's a browser plugin waiting to be written.
It reportedly overwrites a header sent by the client:
Re: How Verizon's Advertising Header Works
#6Universal TLS can't come fast enough.
Re: How Verizon's Advertising Header Works
#7This means that they are doing deep packet inspection and re-writing the actual packets sent over the network, right?
Re: How Verizon's Advertising Header Works
#8[deleted]
Re: How Verizon's Advertising Header Works
#9VPN or TLS ftw
Re: How Verizon's Advertising Header Works
#10This means that they are doing deep packet inspection and re-writing the actual packets sent over the network, right?
I wouldn't call it particularly deep packet inspection—they're just rewriting the http requests.