From c835b1b114a531e7e18634bb4604e515d4883cfa Mon Sep 17 00:00:00 2001 From: YoucTagh Date: Wed, 24 Jan 2024 15:07:05 +0100 Subject: [PATCH] Add clarification on using HEAD vs GET requests --- connegp/index.html | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/connegp/index.html b/connegp/index.html index b6fb592..921be5d 100644 --- a/connegp/index.html +++ b/connegp/index.html @@ -604,6 +604,12 @@

Get Resource by Profile

next most specific profile that the resource representation conforms to. Note that resource representations might conform to more general specifications or other profiles via a hierarchy (i.e. transitively).

+

+ As specified in [[RFC9110]], If the HEAD method is used in a request that specifies preferences in the + profile, media type, or other negotiation dimension, then the response should be the same as for a GET method, + including headers and status code, except that the body MUST be empty. It is important to note that headers, + for which the value is determined only while generating the response content, MAY be omitted. +

If a server redirects to another resource it MUST indicate the selected choice of profile from the list requested by the client and SHOULD indicate a specific narrower profile expected to be returned (if known)