W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

Re: HTTP status code equivalents for file:// operations - compat with xhr

From: Michael A. Puls II <shadow2531@gmail.com>
Date: Tue, 18 Aug 2009 17:51:46 -0400
To: "Nikunj R. Mehta" <nikunj.mehta@oracle.com>
Cc: public-webapps@w3.org
Message-ID: <op.uyvockj11ejg13@sandra-svwliu01>
On Tue, 18 Aug 2009 17:33:24 -0400, Nikunj R. Mehta  
<nikunj.mehta@oracle.com> wrote:

> On Aug 18, 2009, at 12:19 AM, Michael A. Puls II wrote:
>> 4. If file:// access isn't implemented (like in IE), don't have open()  
>> throw. Instead, make this.status be 501.
> This is a breaking change to the XHR spec which asks to throw an error.  
> Have you considered the effect of making the proposed change?


"8. Don't have open() throw for cross-domain security restriction. Instead,
use status code 403."

does the same.

I could live without those changes as long as there was information for  
the security_err exception so that you could tell the difference between  
the 2.

Of course, the "Easier Alternative:" I mentioned in  
might be a better way to do things.

Received on Tuesday, 18 August 2009 21:52:36 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:18 UTC