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.

Sign up for GitHub

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

Jump to bottom

cohttp-eio: Allow retrieving valid "Content-Length" header #930

Closed
bikallem opened this issue Sep 1, 2022 · 0 comments · Fixed by #929
Closed

cohttp-eio: Allow retrieving valid "Content-Length" header #930

bikallem opened this issue Sep 1, 2022 · 0 comments · Fixed by #929

Comments

@bikallem
Copy link
Contributor

bikallem commented Sep 1, 2022

RFC 7230 states that valid "Content-Length" header is an integer value >= 0.

Based on comments #879 (comment)

That's an interesting point. https://www.rfc-editor.org/rfc/rfc7230#section-3.3.2 says:

Any Content-Length field value greater than or equal to zero is valid.
@bikallem bikallem mentioned this issue Sep 1, 2022
Merged
bikallem added a commit to bikallem/ocaml-cohttp that referenced this issue Sep 1, 2022
@bikallem
eio(client) : fix mirage#930
ffa40a6
bikallem added a commit to bikallem/ocaml-cohttp that referenced this issue Sep 1, 2022
@bikallem
eio(client) : fix mirage#930
f1cb1b9
bikallem added a commit to bikallem/ocaml-cohttp that referenced this issue Sep 2, 2022
@bikallem
eio(client) : fix mirage#930
40b46be
bikallem added a commit to bikallem/ocaml-cohttp that referenced this issue Sep 2, 2022
@bikallem
eio(client) : fix mirage#930
eecef68
@mseri mseri closed this as completed in 24f475c Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

cohttp-eio: Add Content-Length header to request/response bikallem/ocaml-cohttp
1 participant
@bikallem