Are you sure? The file path after the domain would not be necessary for an ISP to see, only the domain. I’m not sure how all that works, but it’s definitely not a technical requirement thay they can see the complete URL.
They’d also theoretically see the size of the URL, and the size of the page, along with the transport type. So they can infer a lot of information from the exchange, but they couldn’t say for sure what you were viewing on a specific website.
The ISP can see every domain, but not every page. That’s what HTTPS everywhere was all about.
They can see the entire URL, not just the domain. They just can’t see the contents themselves. But they can still see “dudesfuckingfurniture.com/gettingfreakywithadresser.mpeg”
Edit: I might be wrong
Are you sure? The file path after the domain would not be necessary for an ISP to see, only the domain. I’m not sure how all that works, but it’s definitely not a technical requirement thay they can see the complete URL.
After more research, you might be right. I could have sworn I saw full URLs in my router logs on encrypted sites though. I’ll have to check again.
It’s actually more secure than that.
https://blog.mozilla.org/en/products/firefox/https-protect/
They’d see the URL, but not the specific page.
They’d also theoretically see the size of the URL, and the size of the page, along with the transport type. So they can infer a lot of information from the exchange, but they couldn’t say for sure what you were viewing on a specific website.
When it comes to HTTPS, this is just plain wrong on a technical level.
Yeah, I corrected myself.
The example link doesn’t work :'(
I was ready to go down a rabbit hole there
I’m not sure if that’s a real website. I’m not checking.
Narrator : Vej definitely did in fact check.
Fuck no I ain’t
As always on the Internet, rule 34 applies.
Lol plz no