It's a violation of browsing privacy. It's noone's business how or why I arrived at a webpage.
Re:Google Drive Found Leaking Private Data
by grannyg00se on Thursday July 10, 2014 @08:31AM
(#8014692)
By what edict?
The general default behaviour has always been to let an http server know where you're coming from so that it can take whatever actions appropriate. I don't see how or why there is a fundamental violation of some "browsing privacy" rule here.
Re:Google Drive Found Leaking Private Data
by Dylan16807 on Wednesday July 09, 2014 @12:52PM
(#8010667)
More to worry about, such as?
URLs aren't protected any less than cookies are, and cookies are the standard way of securing login tokens.
Heck with URLs you get the 'secure flag' cookie option for free!
Re:Google Drive Found Leaking Private Data
by grannyg00se on Thursday July 10, 2014 @08:35AM
(#8014705)
Your browsing behaviour in general is being recorded via user patterns, user agent strings, browser configuration, ip address, etc. An interested party can, in general, find out where your browser has been regardless of referer strings. What is so special about the url? It shouldn't contain any information that is meant to be secure.
Re:Google Drive Found Leaking Private Data
by tiglionabbit on Wednesday July 09, 2014 @03:54PM
(#8011870)
Yes they are. Cookies are subject to the same origin policy. The Referer header is not.
Re:Google Drive Found Leaking Private Data
by Dylan16807 on Wednesday July 09, 2014 @09:55PM
(#8013184)
I think you misread. grannyg00se said there is a lot more to worry about than http referers. We don't need a reminder that referer is a problem.
I suppose one might consider their previous url private information, but if that's the case you've go a lot more to worry about than http referers.