W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2009

[whatwg] unexpected use of the CORS specification

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 11 Nov 2009 04:16:04 +1100
Message-ID: <2c0e02830911100916s79a59c15ha068a521c2470c56@mail.gmail.com>
On Mon, Nov 9, 2009 at 12:35 PM, Maciej Stachowiak <mjs at apple.com> wrote:
> On Nov 8, 2009, at 7:25 AM, Adam Barth wrote:
>> I don't see the connection with CORS. ?The browser is free to request
>> whatever URLs it wants. ?The results need not be accessible to
>> content. ?Maybe I'm misunderstanding.
> The proposal at the link was for a method to do URL unshortening as a
> client-side script in the browser. That would indeed require CORS. A feature
> built-in to the browser would not.

Yes, there are different ways to solve this and we can go all the way
to the browser, or leave it to a script. But to push it to a script
(which I think is preferable), we need CORS.

Received on Tuesday, 10 November 2009 09:16:04 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:19 UTC