Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Explicit content length on HEAD requests #444

Merged
merged 1 commit into from
Mar 7, 2022

Conversation

mrsimonbennett
Copy link
Contributor

Hey guys, I am in the process of building a server to site infront of S3

https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.13

"The Content-Length entity-header field indicates the size of the entity-body, in decimal number of OCTETs, sent to the recipient or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET."

Copy link
Member

@clue clue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mrsimonbennett Thank you for filing this PR, changes LGTM!

I've reproduced this locally and can can confirm this changeset is indeed needed to give more control over the Content-Length response header for HEAD requests. This is somewhat related to #429 and #430 merged only recently.

May I ask you to squash your changes into a single commit? 👍

@mrsimonbennett
Copy link
Contributor Author

@clue done :)

@clue clue added this to the v1.7.0 milestone Mar 7, 2022
Copy link
Member

@clue clue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mrsimonbennett Thanks for the update, changes LGTM! :shipit: Keep it up 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants