@@ -361,6 +361,14 @@ Normally `llhttp` would error when a CR is not followed by LF when terminating t
361361request line, the status line, the headers or a chunk header.
362362With this flag only a CR is required to terminate such sections.
363363
364+ ### `void llhttp_set_lenient_optional_cr_before_lf(llhttp_t* parser, int enabled)`
365+
366+ Enables/disables lenient handling of line separators.
367+
368+ Normally `llhttp` would error when a LF is not preceded by CR when terminating the
369+ request line, the status line, the headers, a chunk header or a chunk data.
370+ With this flag only a LF is required to terminate such sections.
371+
364372**Enabling this flag can pose a security issue since you will be exposed to request smuggling attacks. USE WITH CAUTION!**
365373
366374### `void llhttp_set_lenient_optional_crlf_after_chunk(llhttp_t* parser, int enabled)`
@@ -373,6 +381,15 @@ With this flag the new chunk can start immediately after the previous one.
373381
374382**Enabling this flag can pose a security issue since you will be exposed to request smuggling attacks. USE WITH CAUTION!**
375383
384+ ### `void llhttp_set_lenient_spaces_after_chunk_size(llhttp_t* parser, int enabled)`
385+
386+ Enables/disables lenient handling of spaces after chunk size.
387+
388+ Normally `llhttp` would error when after a chunk size is followed by one or more spaces are present instead of a CRLF or `;`.
389+ With this flag this check is disabled.
390+
391+ **Enabling this flag can pose a security issue since you will be exposed to request smuggling attacks. USE WITH CAUTION!**
392+
376393## Build Instructions
377394
378395Make sure you have [Node.js](https://nodejs.org/), npm and npx installed. Then under project directory run:
0 commit comments