News for hackers. Stuff that matters.
Re:XSS in Google Finance by PavlovsCat on Tuesday July 30, 2013 @09:26PM (#6131282)
Yes, but Google Finance is on google.com/finance (for some reason; I'm sure it used to be finance.google.com at some point...).

Cookies set for just subdomain.hostname.com can only be "seen by" that particular subdomain, while cookies set for hostname.com can be seen from hostname.com and any and all subdomains. I think that's why they do it constantly, at least stuff like www.google.com/glass certainly makes no sense otherwise. Why not make a fancy new domain for that? I think it's cookie greed.

Re:XSS in Google Finance by toast0 on Tuesday July 30, 2013 @11:56PM (#6131811)
cookie greed doesn't explain it, because they don't issue any cookies for www.google.com, or at least, I don't have any; they do issue cookies for .google.com, which www and finance can access equally. It's either a branding thing, or a they paid for the fancy load balancer so they're going to use it thing.
Re:XSS in Google Finance by PavlovsCat on Wednesday July 31, 2013 @12:32AM (#6131911)
That's a good point, I stand corrected. Of course, if you wanted to be "minimal" about cookies, you'd have to use a subdomain, but using one doesn't mean anything by itself.