Re: JSON-LD responses for core ontologies don't contain CORS headers; limits browser clients

Alex,

I have added to the relevant .htaccess file the instruction to generate the same CORS headers to rdf-schema as for rdf-syntax-ns. It seems to work on my machine when doing a curl —head; however, I would appreciate if you checked everything on your side, too.

Thanks for flagging this.

Ivan

> On 25 Oct 2020, at 02:25, Alex Kreidler <alexkreidler2020@gmail.com> wrote:
> 
> Sorry, just noticed that the link I provided auto-deletes after 24 hours.
> 
> I've included the full output of the issue below, along with via another pastebin: https://pastebin.com/Jf3K7DW7 <https://pastebin.com/Jf3K7DW7>
> 
> $ http HEAD http://www.w3.org/1999/02/22-rdf-syntax-ns#type <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> "Accept: application/ld+json"
> HTTP/1.1 200 OK
> accept-ranges: bytes
> access-control-allow-credentials: true
> access-control-allow-headers: Link, Location, Content-Type, Accept, Vary
> access-control-allow-methods: GET, HEAD, OPTIONS
> access-control-expose-headers: Location, Link, Vary, Last-Modified, ETag, Allow, Content-Length, Accept
> cache-control: max-age=21600
> content-length: 9198
> content-location: 22-rdf-syntax-ns.jsonld
> content-type: application/ld+json
> date: Sun, 25 Oct 2020 00:08:07 GMT
> etag: "23ee-599d39942e300;599d3996211bf"
> expires: Sun, 25 Oct 2020 06:08:07 GMT
> last-modified: Mon, 16 Dec 2019 15:09:32 GMT
> tcn: choice
> vary: negotiate,accept,accept-charset,upgrade-insecure-requests
> 
> 
> 
> $ http HEAD http://www.w3.org/1999/02/22-rdf-syntax-ns#type
> HTTP/1.1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#typeHTTP/1.1> 200 OK
> accept-ranges: bytes
> access-control-allow-credentials: true
> access-control-allow-headers: Link, Location, Content-Type, Accept, Vary
> access-control-allow-methods: GET, HEAD, OPTIONS
> access-control-allow-origin: *
> access-control-expose-headers: Location, Link, Vary, Last-Modified, ETag, Allow, Content-Length, Accept
> cache-control: max-age=21600
> content-length: 6004
> content-location: 22-rdf-syntax-ns.ttl
> content-type: text/turtle; charset=utf-8
> date: Sun, 25 Oct 2020 00:08:13 GMT
> etag: "1774-599d39942e300;599d3996204ea"
> expires: Sun, 25 Oct 2020 06:08:13 GMT
> last-modified: Mon, 16 Dec 2019 15:09:32 GMT
> tcn: choice
> vary: negotiate,accept,accept-charset,upgrade-insecure-requests
> 
> 
> 
> $ http HEAD https://www.w3.org/2000/01/rdf-schema#range <https://www.w3.org/2000/01/rdf-schema#range> "Accept: application/ld+json"                  
> HTTP/1.1 200 OK
> accept-ranges: bytes
> cache-control: max-age=21600
> content-length: 5604
> content-location: rdf-schema.jsonld
> content-security-policy: upgrade-insecure-requests
> content-type: application/ld+json
> date: Sun, 25 Oct 2020 00:08:54 GMT
> etag: "15e4-586929c3ace00;586929c7c4f1d"
> expires: Sun, 25 Oct 2020 06:08:54 GMT
> last-modified: Mon, 15 Apr 2019 14:38:48 GMT
> strict-transport-security: max-age=15552000; includeSubdomains; preload
> tcn: choice
> vary: negotiate,accept,accept-charset
> 
> 
> 
> $ http HEAD https://www.w3.org/2000/01/rdf-schema#range
> HTTP/1.1 <https://www.w3.org/2000/01/rdf-schema#rangeHTTP/1.1> 200 OK
> accept-ranges: bytes
> access-control-allow-origin: *
> cache-control: max-age=21600
> content-length: 3812
> content-location: rdf-schema.ttl
> content-security-policy: upgrade-insecure-requests
> content-type: text/turtle; charset=utf-8
> date: Sun, 25 Oct 2020 00:09:03 GMT
> etag: "ee4-4f33230d4a800;586929c6c4edd"
> expires: Sun, 25 Oct 2020 06:09:03 GMT
> last-modified: Tue, 25 Feb 2014 02:53:20 GMT
> strict-transport-security: max-age=15552000; includeSubdomains; preload
> tcn: choice
> vary: negotiate,accept,accept-charset
> 


----
Ivan Herman, W3C 
Home: http://www.w3.org/People/Ivan/
mobile: +33 6 52 46 00 43
ORCID ID: https://orcid.org/0000-0003-0782-2704