Timeline for answer to How do browser cookie domains work? by TRiG
Current License: CC BY-SA 2.5
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 30, 2016 at 4:26 | comment | added | Dtipson | It would be useful if this information were exposed in some way from the browser to javascript. Otherwise, it's impossible to programmatically determine whether you can set a cookie on a certain level of domain. You can't check that list with every call after all! | |
| Jun 6, 2015 at 3:24 | comment | added | ZhongYu | True, and maybe you are referring to "dbound". But that may create more problems; like, posing a challenge for http client implementations. | |
| Jun 6, 2015 at 3:17 | comment | added | TRiG | Yes, there's a solution, but it's an exceedingly messy one. This sort of labelling should be baked into the DNS, not done on an ad hoc basis separately. | |
| Jun 5, 2015 at 21:01 | comment | added | ZhongYu | "com.fr" is konwn as "public suffix". cookie domain cannot be public suffix. see rfc 6265 and publicsuffix.org | |
| May 7, 2010 at 14:16 | history | answered | TRiG | CC BY-SA 2.5 |