canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
Privacy/Features/Shortened HTTP Referer header: Difference between revisions
Privacy/Features/Shortened HTTP Referer header (view source)
Revision as of 16:19, 11 July 2011
, 11 July 2011no edit summary
m (clearing in prep for migration to new feature page format) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{FeatureStatus | |||
|Feature name=Shortened HTTP Referer header | |||
|Feature stage=Definition | |||
|Feature health=OK | |||
}} | |||
{{FeatureTeam | |||
|Feature product manager=Sid Stamm | |||
|Feature feature manager=Sid Stamm | |||
|Feature security lead=Curtis Koenig | |||
|Feature privacy lead=Sid Stamm | |||
}} | |||
{{FeaturePageBody | |||
|Feature open issues and risks=* Site breakage (tolerable? need to quantify this) | |||
* User confusion (make it hidden pref?) | |||
|Feature overview=There is the desire to remove the Referer header outright, possibly in favor of the Origin header or something with less information. It can leak sensitive data accidentally and can be abused as a form of ambient authority. Unfortunately, we can't just stop sending it on requests because too many things on the web might break. [[Privacy/2010-10-27 Shorten-Referer Meeting Notes|Sites like Facebook have expressed a desire for a referer-shortening capability]], so this feature benefits both users and site developers. | |||
This feature adds a way to attenuate the information that's sent as the referrer. This is multiple phases: | |||
''Phase 1:'' User global control. In the first phase, we should create a pref so users can select at most how much of the URL is sent as referrer. They will be able to chose a full referrer value, a referrer that is {scheme, host, port, path}, {scheme, host, port}, or just host. | |||
''Phase 2:'' Site-based control. In the second phase, we enable sites to reduce the amount of data transmitted in referrers generated on their site. This is done by the site sending a signal with the HTTP response indicating that outgoing referrers should be reduced. Stripping options should include the same options mentioned in phase 1. One mechanism could be to support [http://www.webkit.org/blog/907/webkit-nightlies-support-html5-noreferrer-link-relation/ the rel="noreferrer" attribute] to omit referers from link clicks. | |||
==== Next steps ==== | |||
* {{new|(Product Manager) Socialize pref idea via mailing list, brown bag, or some public discussion.}} | |||
* {{new|(Feature Team) Nail down user-initiated shortening requirements}} | |||
* {{new|(Feature Team) Nail down server-initiated shortening requirements}} | |||
* {{new|(Engineer?) Make test plan}} | |||
* {{new|(Engineer) Write patch for phase 1 and land}} | |||
* {{new|(Engineer) Write patch for phase 2 and land}} | |||
|Feature users and use cases=; Leaking search terms : From {{bug|587523#c0}}: "An example of this can be seen by searching for 'no knead bread' with Google, and clicking on the 4th search result, which takes you to www.breadtopia.com/basic-no-knead-method/, a page which "helpfully" lets you know that it is aware of the search terms that brought you to the site." | |||
; Outbound link anonymization : Many sites like gmail send outbound links through a common redirect to strip off any information that may be present in the URL. Supporting rel="noreferrer" reduces the need for extra HTTP traffic and redirects. | |||
|Feature requirements=* Test plan must be created and implemented | |||
* Use cases must be clearly outlined and it must be clear how the feature addresses each. | |||
* Initially, Phase 1 (user-set) should not change default behavior until user initiates change. | |||
* Default referer behavior for sites should not change until sites activate attenuation features. | |||
|Feature non-goals=* We are not removing the HTTP referer header | |||
* We are not replacing the HTTP referer header | |||
* This is not the Origin header | |||
|Feature implementation notes=* [http://www.facebook.com/notes/facebook-engineering/protecting-privacy-with-referrers/392382738919 Facebook write-up on "HTTP-Referer" woes] | |||
* [http://www.webkit.org/blog/907/webkit-nightlies-support-html5-noreferrer-link-relation/ the rel="noreferrer" attribute] | |||
* {{bug|587523}}: strip referrer in a future anonymous mode | |||
}} | |||
{{FeatureInfo | |||
|Feature priority=P1 | |||
|Feature roadmap=Privacy | |||
|Feature list=Platform | |||
|Feature engineering team=Networking | |||
}} | |||
{{FeatureTeamStatus | |||
|Feature products status=tbd | |||
|Feature engineering status=tbd | |||
|Feature security status=tbd | |||
|Feature privacy status=tbd | |||
|Feature localization status=tbd | |||
|Feature accessibility status=tbd | |||
|Feature qa status=tbd | |||
|Feature ux status=tbd | |||
}} | |||