isHeaderValueUnsafe

Whether a header value would corrupt the request line if written verbatim: an embedded CR or LF lets the value terminate the current header and inject further headers (or smuggle a request) into the outbound HTTP stream. The raw socket request paths call this as a last line of defence before concatenating a value onto the wire, so even a value that bypassed encodeHeaderValue cannot break framing.

@safe @safe nothrow @nogc
bool
isHeaderValueUnsafe
(
string value
)