sfv
sfv copied to clipboard
undef1nd
Structured HTTP field values parsing and serialization. Implementation of RFC 8941 https://httpwg.org/specs/rfc8941.html
Closes #98 Hej folks, as promised in the related issue, I gave a stab at validating the bare items on construction. ~For the moment I have introduced `BareItem::Validated*` variants adjacent...
While I was waiting for the review on #102 I was eager to learn a bit more and found that the date support was a nice hook for me to...
sfv implements parsing validation, per the rules in RFC 8941. For example, Tokens are checked for valid character usage in https://github.com/undef1nd/sfv/blob/master/src/parser.rs#L290 However, I might have missed it but there doesn't...
This simplifies the interface while simultaneously making the function more general.
1. `GenericBareItem` has two additional variants: `Date` and `DisplayString`. 2. Parsing accepts a `Format` enum that controls whether dates and display strings are permitted. The newer RFC 9651 is the...
[RFC 9651](https://httpwg.org/specs/rfc9651.html) adds Date and Display String bare item types. The actual parsing and serialization code for these isn't complicated, but design-wise we could integrate them in a few different...
These conditions are only possible when the individual bare-item parsing methods are called directly, but that is only possible in tests.