Link header in all responses to requests made to LDPRs

[fserena]

The specification says:

4.2.1.4 LDP servers exposing LDPRs must advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#Resource, and a link relation type of type (that is, rel='type') in all responses to requests made to an LDPR's HTTP Request-URI [RFC5988].

As far as I've seen, basic tests that perform GET and/or OPTIONS methods are checking this header in the responses. But the same doesn't occur with the other methods (POST, PUT, ...), except for the NonRDFSource tests.

Is there any reason why this is so? (if I'm right)

[sspeiche]

We have separate tests to verify this. I believe the testing methodology isn't to exhaustively test each request but focus on the conformance requirement being tested.

We could check ALL responses we receive from ALL requests everywhere in the test suite, perhaps that would be valuable. Seems a little heavy to me but we should be consistent.

[spadgett]

We might add a test that cycles through the HTTP methods from Allow and checks the Link header in responses to each.