2 Commits

Author	SHA1	Message	Date
benoitc	555d2fa27f	don't tolerate wrong te headers ... changes: - Just follow the new TE specification (https://datatracker.ietf.org/doc/html/rfc9112#name-transfer-encoding) here and accept to introduce a breaking change. - gandle multiple TE on one line ** breaking changes ** : invalid headers and position will now return an error.	2024-08-06 23:47:01 +02:00
Paul J. Dorn	ac29c9b0a7	fail-safe on unsupported request framing ... If we promise wsgi.input_terminated, we better get it right - or not at all. * chunked encoding on HTTP <= 1.1 * chunked not last transfer coding * multiple chinked codings * any unknown codings (yes, this too! because we do not detect unusual syntax that is still chunked) * empty coding (plausibly harmless, but not see in real life anyway - refused, for the moment)	2023-12-15 13:33:31 +01:00