- From: Dave Longley <dlongley@digitalbazaar.com>
- Date: Tue, 30 Dec 2014 21:50:59 -0500
- To: Gregg Kellogg <gregg@greggkellogg.net>, Linked JSON <public-linked-json@w3.org>
- CC: Markus Lanthaler <markus.lanthaler@gmx.net>
I changed the nameservers back to the original server, so hopefully this will go away once the changes propagate. Still, this is something good to keep in mind should we need a backup server again (hopefully not :)). On 12/30/2014 06:58 PM, Gregg Kellogg wrote: > After json-ld.org was re-hosted, we lost something. I'm failing some remote-doc tests, it looks like because some .json files are returning text/plain instead of application/json. For example: > > curl -I http://json-ld.org/test-suite/tests/remote-doc-0002-in.json > HTTP/1.1 200 OK > Date: Tue, 30 Dec 2014 23:55:20 GMT > Content-Type: text/plain > Content-Length: 95 > Connection: keep-alive > Set-Cookie: __cfduid=d59fecab8352cd6e9d166b0ab3a0085601419983720; expires=Wed, 30-Dec-15 23:55:20 GMT; path=/; domain=.json-ld.org; HttpOnly > Last-Modified: Tue, 23 Dec 2014 18:50:23 GMT > ETag: "f68539b-5f-50ae6a5c0b544" > Accept-Ranges: bytes > Vary: User-Agent > Server: cloudflare-nginx > CF-RAY: 1a122aea5dfd0296-SJC > > There isn't a specific rule in the .htaccess for that directory, so it must have been an httpd.conf setting on the original server. > > I get the errors specifically for remote-doc-0002-in.json, remote-doc-0010-in.json, and remote-doc-0012-in.json. > > Gregg Kellogg > gregg@greggkellogg.net > -- Dave Longley CTO Digital Bazaar, Inc.
Received on Wednesday, 31 December 2014 02:51:23 UTC