5 ms·
Why is that the responsibility of the browser and not the website's owner?
by scrollaway 10y ago
Why is that the responsibility of the browser and not the website's owner?
- spiderfarmer 10y agoI don't understand either, with user generated subdomains I thought it was common practice to use a completely different domain for all trusted activity.
- jerf 10y agoNothing profound, just historical reasons. To really show the problem, you have to do something like contrast how "blogspot.com" is a top-level site, one level below a TLD, but so is bbc.co.uk, one level below what "co.uk". The naive "count one element" doesn't work, or all of "co.uk" would share cookies. And it turns out that now there just isn't much you can do other than have a huge table. Sure, we'd probably do it differently if we had it to do all over again, but, we don't.
- scrollaway 10y agoYou misunderstood. I fully understand why a count based approach cannot work. I don't understand why, should I want to create a service like blogspot, I would have to have my URL added in there.
- Manishearth 10y agoYou don't have to add it there. You can make it secure anyway. Public suffix list will mean that should your security get messed up, the browser prevents this anyway.