Hi Maarten, > On 24 May 2024, at 15:27, Maarten Wullink <maarten.wull...@sidn.nl> wrote: > > Hi Gavin, > > Like Marc, i’m not a big fan of duplicating the link information from the > json response into the response headers. > However, for the HEAD method request i do see a use case, because in this > case there exists no data duplication and the client can efficiently navigate > the Link headers in the response. > > anyway, just my 2 cent.
Yes I agree. The reason why the link headers are included in the GET response is because the HTTP specification says that for the same resource, the headers have to be the same for both HEAD and GET. So to get them in the HEAD response (which is where they bring benefit) they have to be present in the GET response. G. -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org