Skip to content

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

Description

@leske42
  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).

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions