Strange maybe compound bug GET https://databox.me/,proxy?uri=http%3A%2F%2Flocalhost%3A3080%2Ftimbl%2FPublic%2FPublicTypeIndex.ttl net::ERR_EMPTY_RESPONSE That is from chrome JS console. $ curl https://databox.me/,proxy?uri=http%3A%2F%2Flocalhost%3A3080%2Ftimbl%2FPublic%2FPublicTypeIndex.ttl curl: (52) Empty reply from server That is from curl. So the proxy is definitely broken. Same happens with a HEAD request: curl -I https://databox.me/,proxy?uri=http%3A%2F%2Flocalhost%3A3080%2Ftimbl%2FPublic%2FPublicTypeIndex.ttl curl: (52) Empty reply from server That said, the original resource being proxied is a bit strange. It has a content-length of 2 in a HEAD: `` $ curl -I http://localhost:3080/timbl/Public/PublicTypeIndex.ttl HTTP/1.1 200 OK X-Powered-By: Express Link: <PublicTypeIndex.ttl.acl> rel="acl", <PublicTypeIndex.ttl.meta> rel="describedBy", <http://www.w3.org/ns/ldp#Resource> rel="type" Vary: Origin Access-Control-Allow-Credentials: true Access-Control-Expose-Headers: User, Location, Link, Vary, Last-Modified, Content-Length MS-Author-Via: SPARQL Updates-Via: http://localhost:3080 Content-Type: text/plain; charset=utf-8 Content-Length: 2 ETag: W/"2-4KoCHiHd29bYzs7HHpz1ZA" set-cookie: connect.sid=s%3A1M4dZlcCPpfdrXlzHj7qdzJGIQXwDqTG.j2qJWrO1B0OKg7MJ%2FEhnxv0xgcJsR802ZQ0XC8RyRL4; Path=/; HttpOnly Date: Wed, 17 Feb 2016 11:30:05 GMT Connection: keep-alive timbl 06:35 well that was my localhost copy. The copy on https://timbl.com/ does the same What happens when we GET the original file from ldnode? $ curl -v https://timbl.com/timbl/Public/PublicTypeIndex.ttl * Trying 73.218.51.127... * Connected to timbl.com (73.218.51.127) port 443 (#0) * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 * Server certificate: timbl.com > GET /timbl/Public/PublicTypeIndex.ttl HTTP/1.1 > Host: timbl.com > User-Agent: curl/7.43.0 > Accept: */* > < HTTP/1.1 200 OK < X-Powered-By: Express < Link: <PublicTypeIndex.ttl.acl> rel="acl", <PublicTypeIndex.ttl.meta> rel="describedBy", <http://www.w3.org/ns/ldp#Resource> rel="type" < Vary: Origin < Access-Control-Allow-Credentials: true < Access-Control-Expose-Headers: User, Location, Link, Vary, Last-Modified, Content-Length < MS-Author-Via: SPARQL < Updates-Via: https://timbl.com < Content-Type: text/turtle < set-cookie: connect.sid=s%3Ad5FCDhbngX14k2LcLhIJU9sytdmn34ps.3XR3%2B9Km5zcsq5Mqzh%2Fj0p%2FkTAsxzf2dNKHY6361zJM; Path=/; HttpOnly; Secure < Date: Wed, 17 Feb 2016 11:34:34 GMT < Connection: keep-alive < Transfer-Encoding: chunked < @prefix n: <http://www.w3.org/2006/vcard/ns#>. @prefix terms: <https://www.w3.org/ns/solid/terms#>. @prefix boo: <http://localhost:3080/timbl/2016/02/01/test1/book.ttl#>. n:AddressBook terms:instance boo:this . * Connection #0 to host timbl.com left intact $ A weird thing there is there is no content-length sent at all. Is that an excuse for the proxy to disconnect? But it should sent the content-length, even if it uses streaming internally. So this looks like three bugs - The bad content-length of 2 on a HEAD - the missing content-length (I mean) on the GET (from ldnode) - in gold, the bad reaction in closing down the client connection, whcih should not happen even if no content-length
