Don't send content in responses to HEAD requests

[James Pic]

Responses to HEAD requests must not send content as per RFC9110

9.3.2. HEAD
The HEAD method is identical to GET except that the server MUST NOT send content in the response.

​https://www.rfc-editor.org/rfc/rfc9110.html#name-head

Currently, Django sends content in response to HEAD requests.

Django *MUST NOT* send content in response for HEAD requests.

Demonstration:

$ django-admin startproject test
$ cd test && ./manage.py runserver
# tcpdump -vv -s0 -A -i lo port 8000 &> tcpdump.txt
$ curl -I localhost:8000

tcpdump.txt attached, it shows Django sends content in the HEAD response

[David Sanders]

Thanks for the report but it's not clear what issue you are reporting with Django. Feel free to update the ticket with more context; closing for now pending more information.

[James Pic]

Do you want a description like this?

Currently, Django sends content in responses to HEAD requests.
Django MUST NOT send content in responses to HEAD requests, as per RFC9110;
The HEAD method is identical to GET except that the server MUST NOT send content in the response.
​https://www.rfc-editor.org/rfc/rfc9110.html#name-head

Is that better or do you think we need more?

[James Pic]

Updated the description, I think it's now pretty understandable even with little understanding of Django and HTTP ;)

[Mariusz Felisiak]

Duplicate of #28054 (fixed in 8acc433e415cd771f69dfe84e57878a83641e78b).

[James Pic]

Thanks you very much!