Version 1.1.2

httpsfv 1.1.2 sharpens RFC 9651 conformance. Two parsing edge cases are fixed, and the library is now validated against the complete official httpwg test suite, 1592 cases refreshed to the latest upstream revision, on every push. Recommended for anyone serializing maximal-length integers or parsing fields split across multiple lines.

🐛 Bug Fixes

• Numbers: Do not reject a maximal-length number followed by a delimiter. The length bound was checked before consuming the next character, so a 15-digit integer or 16-digit decimal failed as soon as anything followed it: a comma, a semicolon, an equals sign. This meant the library could serialize headers it then refused to parse back, such as 123456789012345, 1. by @youdie006 in #15
• Parsing: Join multi-line field values with ", " rather than ",", as RFC 9651 section 4.2 requires. A string split across two field lines now parses to foo, bar instead of foo,bar. If you pass multiple field lines to UnmarshalItem, UnmarshalList or UnmarshalDictionary, this changes the parsed result. by @dunglas in #16

💖 New Contributors

• @youdie006 made their first contribution in #15

Full Changelog: v1.1.1...v1.1.2