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

[manifest] Parsing origins, was Re: Review of Web Application Manifest Format and Management APIs

From: Marcos Caceres <w3c@marcosc.com>
Date: Fri, 25 May 2012 15:39:54 +0100
To: Anant Narayanan <anant@mozilla.com>
Cc: Marcos Caceres <marcosscaceres@gmail.com>, public-webapps@w3.org
Message-ID: <6F81833553A54A59A76FF69AEC75BD48@marcosc.com>

Hi Anant,  

On Sunday, May 13, 2012 at 5:47 PM, Anant Narayanan wrote:

> > > installs_allowed_from: An array of origins that are allowed to trigger installation of this application. This field allows the developer to restrict installation of their application to specific sites. If the value is omitted, installs are allowed from any site.
> > 
> > 
> > 
> > How are origins parsed?
> 
> I'm not sure what the question means, but origins are essentially a
> combination of [protocol]://[hostname]:[port]. Whenever an install is
> triggered, the UA must check if the origin of the page triggering the
> install is present in this array. * is a valid value for
> installs_allowed_from, in which case the UA may skip this check.

By parsing I mean which ones win, which ones get discarded, what happens to invalid ones, are they resolved already, etc. in the following:

installs_allowed_from: [ "   http://foo/ ", "bar://", 22, "https://foo/bar/#*", "http://foo:80/", "wee!!!", "http://baz/hello there!", "http://baz/hello%20there!"]

And so on. So, all the error handling stuff. Or is a single error fatal? 
Received on Friday, 25 May 2012 14:42:31 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT