W3C home > Mailing lists > Public > public-tracking@w3.org > February 2012


From: Aleecia M. McDonald <aleecia@aleecia.com>
Date: Sat, 4 Feb 2012 18:15:21 -0500
To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
Message-Id: <82E081D2-78B7-4355-B051-4C2D36987489@aleecia.com>
Issue housekeeping. I'm resending this with the issue number attached (which did not exist when Karl sent his message) so we can find this thread again by issue number. 

I had assumed there were no data collection implications for referrer, only potential data use issues. Given the current debate, we might future-proof with a MAY or SHOULD, but it seems entirely premature to try MUST when this is a live issue that may or may not go anywhere. Or, we could do nothing at all. Right now issue-122 is raised rather than open simply because we have enough other work to do between now and publishing the next public working draft. We'll take it up in a few weeks.


Begin forwarded message:

> Resent-From: public-tracking@w3.org
> From: Karl Dubost <karld@opera.com>
> Subject: meta referer in HTML
> Date: January 30, 2012 5:08:55 PM EST
> To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
> FYI,
> there is a discussion going on about a meta referer. The Pros and Cons have been outlined in the WHAT WG wiki [1].
>    This document describes a proposal the "referrer" 
>    metadata name. Using the referrer metadata attri-
>    bute, a document can control the behavior if the 
>    Referer HTTP header attached to requests that 
>    originate from the document.
> In the markup, it would look like:
>    <meta name="referrer" content="never">
> with following values : never, always, origin, default
> [1]: http://wiki.whatwg.org/wiki/Meta_referrer
> -- 
> Karl Dubost - http://dev.opera.com/
> Developer Relations, Opera Software

Received on Saturday, 4 February 2012 23:15:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:38:33 UTC