#35051: HEAD Responses Drop Headers
-------------------------------+--------------------------------------
Reporter: Paul Bailey | Owner: nobody
Type: New feature | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Natalia Bidart):
* status: new => closed
* severity: Release blocker => Normal
* resolution: => invalid
* version: 5.0 => dev
* type: Bug => New feature
* stage: Accepted => Unreviewed
Comment:
Replying to [comment:2 Mariusz Felisiak]:
> I don't agree, we intentionally drop the `Content-Length`. Please check
the entire discussion in PR, e.g. this
[https://github.com/django/django/pull/16502#issuecomment-1405617633
comment]. As far as I'm aware, the current implementation is RFC
compliant. I'd mark this ticket as invalid.
Thank you Mariusz for the pointer to the specific message from Nick, it
provides a very complete and clear reasoning for the change.
With that in mind, I agree that this is not a valid **bug**. Additionally,
I agree that the optional return of `Content-Length` for `HEAD` requests,
enabling specific use cases, should be approached as a new feature, which
should be presented and discussed in the
[https://forum.djangoproject.com/c/internals/5 Django Forum] (following
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features the documented guidelines for requesting
features]). Paul, would you be willing to start a new topic explaining the
current situation and outlining potential use cases for the feature?
--
Ticket URL: <https://code.djangoproject.com/ticket/35051#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018c878acdf4-7a716e6e-6735-42b3-a8bb-c49ff6027541-000000%40eu-central-1.amazonses.com.
