Unusual content-negotiation responses on a "meta" LDP URI

Hi again!

I believe this is a bug.

I have an LDP Container …/fair/
It has a rel-meta: …/fair,meta

If I call …/fair,meta using GET with “Accept: text/turtle” it responds with a 406 Unacceptable.
If I call …/fair,meta using GET with default Accept headers it responds with 200 OK, Content-type: text/html, but the body is a Turtle document (i.e. not HTML)

So… two bugs, I guess:

  1. content negotiation for Turtle fails, even though Turtle is available, and
  2. content-type header is incorrect for a returned Turtle document

Cheers guys!