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

Content-Length is empty on HEAD #209

Closed
gerhardj-b opened this issue Oct 10, 2022 · 2 comments · Fixed by #219
Closed

Content-Length is empty on HEAD #209

gerhardj-b opened this issue Oct 10, 2022 · 2 comments · Fixed by #219
Assignees

Comments

@gerhardj-b
Copy link

This is not according to the S3 API as well as HTTP standards.

My client relies on the content length returned by the HEAD request. Is it therefore possible to change this, so that the content-length is also sent on such requests?

@jakobvogel
Copy link
Member

Many thanks for reporting this @gerhardj-b ☺️ … Can you please be more precise? Which operations exactly expect the content-length and we fail to provide it?

@jakobvogel
Copy link
Member

I have found one such condition on PUTing an object. Do you refer to this?

jakobvogel added a commit that referenced this issue Feb 23, 2023
This avoids warnings by the AWS client software.

#209
SIRI-721

Signed-off-by: Jakob Vogel <jvo@scireum.de>
jakobvogel added a commit that referenced this issue Feb 23, 2023
Signed-off-by: Jakob Vogel <jvo@scireum.de>

#209
jakobvogel added a commit that referenced this issue Feb 24, 2023
Signed-off-by: Jakob Vogel <jvo@scireum.de>

#209
jakobvogel added a commit that referenced this issue Feb 24, 2023
#209
SIRI-721

Signed-off-by: Jakob Vogel <jvo@scireum.de>
jakobvogel added a commit that referenced this issue Feb 24, 2023
#209
SIRI-721

Signed-off-by: Jakob Vogel <jvo@scireum.de>
jakobvogel added a commit that referenced this issue Feb 24, 2023
#209
SIRI-721

Signed-off-by: Jakob Vogel <jvo@scireum.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants