Nimbostratus
NimbostratusHello All,
I realize this is an older post but it is one that comes up when searching on LWS issues with F5. Therefore I wanted to post an answer here as well. The primary controlling RFC for HTTP over the last 20 years has be RFC 2616. Where it adopted header folding or LWS folding from the SMTP specification. LWS folding places the newline and space "0x000a0x0020" characters every N characters (78 called out by earlier SMTP RFC with a maximum length of 998). The latest RFC group which now obsoletes RFC 2616 and to which newer updates to browsers are written to be compliant with, is RFC 7230. In RFC 2616 Section 4.2 Message Headers it states - "Header fields can be extended over multiple lines by preceding each extra line with at least one SP or HT" but in RFC 7230 Section 3.2.4 Field Parsing:
"Historically, HTTP header field values could be extended over
multiple lines by preceding each extra line with at least one space
or horizontal tab (obs-fold). This specification deprecates such
line folding except within the message/http media type
(Section 8.3.1). A sender MUST NOT generate a message that includes
line folding (i.e., that has any field-value that contains a match to
the obs-fold rule) unless the message is intended for packaging
within the message/http media type."
Therefore for API "HTTP::header insert" commands should no longer use the LWS qualifier to insert Linear White Space to HTTP headers for newer implementations.
Regards,
Kevin