Skip to content

ContentLengthWithTransferEncoding

[Source]

A request carries both Content-Length and Transfer-Encoding header fields.

RFC 9112 §6.3 forbids this combination ("A sender MUST NOT send a Content-Length header field in any message that contains a Transfer-Encoding header field") because it is a request-smuggling vector: an intermediary that honors one header while Stallion honors the other can be desynchronized, letting a smuggled request slip past. Rather than pick a framing, Stallion rejects the message — the presence of both headers is itself the fault, regardless of what either header's value resolves to.

primitive val ContentLengthWithTransferEncoding

Constructors

create

[Source]

new val create()
: ContentLengthWithTransferEncoding val^

Returns

Public Functions

string

[Source]

fun box string()
: String iso^

Returns

eq

[Source]

fun box eq(
  that: ContentLengthWithTransferEncoding val)
: Bool val

Parameters

Returns

ne

[Source]

fun box ne(
  that: ContentLengthWithTransferEncoding val)
: Bool val

Parameters

Returns