W3C home > Mailing lists > Public > public-linked-json@w3.org > March 2017

Re: cors error when loading json files

From: Robert Sanderson <azaroth42@gmail.com>
Date: Thu, 23 Mar 2017 10:43:48 -0700
Message-ID: <CABevsUEkbY80zJ9=KVZdDQhR6C-Fr_ZadvF8C-hQqRW_E4uj8A@mail.gmail.com>
To: Brent Shambaugh <brent.shambaugh@gmail.com>
Cc: Linked JSON <public-linked-json@w3.org>
The ACAO should not be "*, *" just "*"

This commonly happens when there are conflicting apache AddHeader rules
rather than SetHeader ... if you AddHeader ACAO *, and some previous system
has done the same, you end up with the comma separated list.

HTH,

Rob

On Thu, Mar 23, 2017 at 10:13 AM, Brent Shambaugh <brent.shambaugh@gmail.com
> wrote:

> Is this quite expected with json-ld files, such as the example at
> json-ld.org?
>
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading
> the remote resource at http://json-ld.org/contexts/person.jsonld.
> (Reason: CORS header ‘Access-Control-Allow-Origin’ does not match ‘*,
> *’).  (unknown)
>
> -Brent Shambaugh
>
> GitHub: https://github.com/bshambaugh
> Website: http://bshambaugh.org/
> LinkedIN: https://www.linkedin.com/in/brent-shambaugh-9b91259
> Skype: brent.shambaugh
> Twitter: https://twitter.com/Brent_Shambaugh
>
>


-- 
Rob Sanderson
Semantic Architect
The Getty Trust
Los Angeles, CA 90049
Received on Thursday, 23 March 2017 17:44:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:49 UTC