nodeSolidServer / nodeSolidServer/node-solid-server

HTTP 500 error fetching JSON LD from solid.community

Offen
#1,332 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@jaxoncreed arbeitet bereits daran.

Seit 29.10.2019.

Vorherrschende Sprache
JavaScript
Sterne
1.8k
Forks
308
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

15:32:24 jonathan:~ (master) $ curl -v "https://kayakr.solid.community/profile/card" -H "Accept:application/ld+json"

*   Trying 165.227.231.225...
* TCP_NODELAY set
* Connected to kayakr.solid.community (165.227.231.225) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=solid.community
*  start date: Sep 29 13:01:54 2019 GMT
*  expire date: Dec 28 13:01:54 2019 GMT
*  subjectAltName: host "kayakr.solid.community" matched cert's "*.solid.community"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
> GET /profile/card HTTP/1.1
> Host: kayakr.solid.community
> User-Agent: curl/7.54.0
> Accept:application/ld+json
> 
< HTTP/1.1 500 Internal Server Error
< X-Powered-By: solid-server/5.2.0
< Vary: Accept, Authorization, Origin
< Access-Control-Allow-Credentials: true
< Access-Control-Expose-Headers: Authorization, User, Location, Link, Vary, Last-Modified, ETag, Accept-Patch, Accept-Post, Updates-Via, Allow, WAC-Allow, Content-Length, WWW-Authenticate
< Allow: OPTIONS, HEAD, GET, PATCH, POST, PUT, DELETE
< Link: <card.acl>; rel="acl", <card.meta>; rel="describedBy", <http://www.w3.org/ns/ldp#Resource>; rel="type"
< WAC-Allow: user="read",public="read"
< MS-Author-Via: SPARQL
< Updates-Via: wss://kayakr.solid.community
< Content-Type: text/plain; charset=utf-8
< Content-Length: 38
< ETag: W/"26-QBI7EYtDt6zJzGYxyvtGCQrnW5Q"
< Date: Sat, 26 Oct 2019 02:35:53 GMT
< Connection: keep-alive
< 
Error translating between RDF formats
* Connection #0 to host kayakr.solid.community left intact

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.