- From: Dan Brickley <danbri@google.com>
- Date: Fri, 16 Sep 2016 16:15:02 +0100
- To: Thomas Francart <thomas.francart@sparna.fr>
- Cc: Alexandre Bertails <bertails@apple.com>, "schema.org Mailing List" <public-schemaorg@w3.org>, Markus Lanthaler <lanthaler@google.com>, Richard Wallis <richard.wallis@dataliberate.com>
- Message-ID: <CAK-qy=7weKKmQh2RNhuPcK5wdcaYd=OncuDM2Z1C=o4j5RfMjA@mail.gmail.com>
+Richard, Markus, We ran into some problems due to the content negotiation. It's possible there's another route but for now the redirect seemed the best fix. Details at https://github.com/schemaorg/schemaorg/issues/1219 but for example users of the JSON-LD Playground were finding it fail if they had the HTML flavour of http://schema.org/ cached in their browser. I am not sure if the problem was Chrome only or others too. Dan On 16 September 2016 at 15:56, Thomas Francart <thomas.francart@sparna.fr> wrote: > Thanks > > Using an extra flag to follow redirects actually works : > > curl -L --header "Accept: application/ld+json" http://schema.org > > Thomas > > > 2016-09-16 16:54 GMT+02:00 Alexandre Bertails <bertails@apple.com>: > >> I noticed a redirect was introduced a few days ago: >> >> [[ >> ➜ http HEAD http://schema.org Accept:application/ld+json >> HTTP/1.1 302 Found >> Access-Control-Allow-Origin: * >> Age: 18 >> Cache-Control: public, max-age=600 >> Content-Length: 0 >> Content-Type: text/html; charset=utf-8 >> Date: Fri, 16 Sep 2016 14:52:21 GMT >> Location: http://schema.org/docs/jsonldcontext.json >> Server: Google Frontend >> Vary: Accept, Accept-Encoding >> X-Cloud-Trace-Context: 04558cad20e4b9047bcaf137b8e11852 >> ]] >> >> It wasn't there before and I've had to update my software too. >> >> I bet most libraries are not expecting to follow redirects either. >> >> Best, >> Alexandre >> >> > On Sep 16, 2016, at 7:48 AM, Thomas Francart <thomas.francart@sparna.fr> >> wrote: >> > >> > Hello >> > >> > I remember this worked a few weeks ago : >> > >> > curl --header "Accept: application/ld+json" http://schema.org >> > >> > Now it doesn't. >> > >> > And any JSON-LD declaring "@context" : "http://schema.org" can't be >> parsed anymore : >> > >> > "Caused by: com.github.jsonldjava.core.JsonLdError: loading remote >> context failed: http://schema.org" >> > >> > Any idea what can go wrong ? >> > Is there any best practice or workaround for caching a JSON-LD context ? >> > >> > Cheers >> > Thomas >> > >> > -- >> > >> > Thomas Francart - SPARNA >> > Web de données | Architecture de l'information | Accès aux connaissances >> > blog : blog.sparna.fr, site : sparna.fr, linkedin : >> fr.linkedin.com/in/thomasfrancart >> > tel : +33 (0)6.71.11.25.97, skype : francartthomas >> >> > > > -- > > *Thomas Francart* -* SPARNA* > Web de *données* | Architecture de l'*information* | Accès aux > *connaissances* > blog : blog.sparna.fr, site : sparna.fr, linkedin : fr.linkedin.com/in/ > thomasfrancart > tel : +33 (0)6.71.11.25.97, skype : francartthomas >
Received on Friday, 16 September 2016 15:15:47 UTC