Re:Google Drive Found Leaking Private Data
by esrauch on Wednesday July 09, 2014 @12:02PM
(#8010352)
This never made sense to me, why was this behavior defined this way and why has no browser challenged it? A more rational rule would be something like "only send header if the referer url is http, or if the referer and destination have exact match hosts"
[ Parent
| on HN ]
Re:Google Drive Found Leaking Private Data
by nucleardog on Wednesday July 09, 2014 @09:19PM
(#8013104)
Because the spec and implementations came along well before we started putting HTTPS on everything, or even most/many things. Given the number of HTTPS->HTTPS links you would have run across in regular practice the spec and your proposal were probably more or less identical in practice.
As for why it's still that way... I'm sure no one has bothered to really think about it since.