Summary

Content negotiation returns text/turtle regardless of the order specified in the Accept header.

Steps to Reproduce

curl -I 'https://example.com/' -H 'Accept: application/ld+json, text/turtle, application/json'

Expected: Content-Type: application/ld+json (first in list)

Actual: Content-Type: text/turtle

Workaround

Request only the desired type:

curl -I 'https://example.com/' -H 'Accept: text/html'

This correctly returns Content-Type: text/html.

Impact

• Clients cannot reliably request preferred content types
• WebID-TLS verification fails when expecting JSON-LD but receiving Turtle (see WebID-TLS: Fix Accept header and JSON-LD regex for HTML profiles #70)
• Breaks standard HTTP content negotiation behavior per RFC 7231

Environment

• JSS v0.0.75