W3C home > Mailing lists > Public > public-webplatform@w3.org > October 2013

Re: Didn't we enable CORS?

From: Julee Burdekin <jburdeki@adobe.com>
Date: Wed, 23 Oct 2013 18:04:56 -0700
To: Renoir Boulanger <renoir@w3.org>, Julee <julee@adobe.com>
CC: List WebPlatform public <public-webplatform@w3.org>, David Kirstein <frozenice@frozenice.de>, Ryan Lane <rlane32@gmail.com>
Message-ID: <CE8DBFE1.9B194%jburdeki@adobe.com>
Hi, Renoir:

I thought that Frozenice was wanting to open CORS to everyone, maybe with a blacklist. And we talked about having some hurdles for POST requests. For example, the email API I want to use requires a token. So I think we're good there.

Regards.

Julee


----------------------------
julee@adobe.com
@adobejulee




-----Original Message-----
From: Renoir Boulanger <renoir@w3.org<mailto:renoir@w3.org>>
Date: Wednesday, October 23, 2013 7:34 AM
To: julee <julee@adobe.com<mailto:julee@adobe.com>>
Cc: WebPlatform Public List <public-webplatform@w3.org<mailto:public-webplatform@w3.org>>, David Kirstein <frozenice@frozenice.de<mailto:frozenice@frozenice.de>>, Ryan Lane <rlane32@gmail.com<mailto:rlane32@gmail.com>>
Subject: Re: Didn't we enable CORS?

I just read the thread I referred to.

I agree with Frozenice, I prefer to explicitly allow when it is acceptable to give away.

Our upcoming 'data.webplatform.org' could have it though. But I assume we would include automatically some attribution link along with the data it provides.

So, to continue on the e-mail form situation, Julee, please tell me which form you have problem with CORS and i'll see what I can do.

Renoir
~
Received on Thursday, 24 October 2013 01:05:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:13:55 UTC