W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: HTML5 Origin (aka IETF Origin draft)

From: Adam Barth <w3c@adambarth.com>
Date: Fri, 10 Apr 2009 11:01:19 -0700
Message-ID: <7789133a0904101101x656b37d0n99be3eb3cec3675c@mail.gmail.com>
To: Bil Corry <bil@corry.biz>
Cc: public-webapps@w3.org
This is to support things like data URLs that can't be represented as
a (scheme, host, port) tuple.


On Thu, Apr 9, 2009 at 9:48 AM, Bil Corry <bil@corry.biz> wrote:
> I wanted to clarify something in the IETF Origin draft[1], which is now going to serve as the basis for HTML5's Origin.
> Section 5 requires that when a user agent provides the Origin header, it must either send "null" or the ASCII serialization of the origin.  ASCII serialization (and Unicode serialization) stipulates that if an origin is not a scheme/host/port tuple, then it must return "null".  Section 2 allows implementations to define other types of origins in addition to the scheme/host/port tuple.  So my question is, if a user agent defines another type of origin, but is required to send "null" for it in the Origin header, is there some other use for defining other types of origins?
> - Bil
> [1] http://www.ietf.org/internet-drafts/draft-abarth-origin-00.txt
Received on Friday, 10 April 2009 18:02:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:12:53 UTC