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

[KNOWN ISSUE] Valid request but Content Length mismatch #105

Open
leske42 opened this issue Dec 1, 2024 · 0 comments
Open

[KNOWN ISSUE] Valid request but Content Length mismatch #105

leske42 opened this issue Dec 1, 2024 · 0 comments

Comments

@leske42
Copy link
Collaborator

leske42 commented Dec 1, 2024

  1. If a valid Content-Length header field is present without
    Transfer-Encoding, its decimal value defines the expected message
    body length in octets. If the sender closes the connection or
    the recipient times out before the indicated number of octets are
    received, the recipient MUST consider the message to be
    incomplete and close the connection [RFC 7230 3.3.3]

Because of TCP or read buffer length we might not receive the whole body at once even if they send with content-length option. Then we need a way to decide if we deal with mismatched body size or not (maybe we need to implement some timeout functionality).

@leske42 leske42 changed the title [KNOWN ISSUE] Content Length mismatch [KNOWN ISSUE] Valid request but Content Length mismatch Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant