- From: Kévin Dunglas <kevin@dunglas.fr>
- Date: Mon, 21 Sep 2020 19:41:47 +0200
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <CADU7aosi1YXGSftfr1h_ych1vkJeyiWqKToo_XW=vD6nBQdBQw@mail.gmail.com>
Hi,
For the record, I also published a parser for Go:
https://github.com/dunglas/httpsfv
Cheers
On Sun, Sep 20, 2020 at 5:32 PM Dmitri Tikhonov <dtikhonov@litespeedtech.com>
wrote:
> Hi Mark,
>
> Yes, the test suite was a great help to shake the bugs out. All the
> tests pass.
>
> ("Pass" in the sense that the parser succeeds where expected and
> fails where expected. The results of the parsing are not verified
> programmatically: that's because the test program does not reconstruct
> the input. I eyeballed a bunch of parsing results, however: they all
> check out.)
>
> - Dmitri.
>
> On Sun, Sep 20, 2020 at 03:38:06PM +1000, Mark Nottingham wrote:
> > That's great, Dmitri!
> >
> > Are you using the test suite?
> >
> > Cheers,
> >
> >
> > > On 20 Sep 2020, at 3:05 pm, Dmitri Tikhonov <
> dtikhonov@litespeedtech.com> wrote:
> > >
> > > On Wed, Aug 21, 2019 at 06:29:06PM +1000, Mark Nottingham wrote:
> > >> I'd also love to get some more implementation diversity.
> > >
> > > I realize I am a little late to the party -- but now there is
> > > a structured fields parser in C:
> > >
> > > https://github.com/litespeedtech/ls-sfparser
> > >
> > > - Dmitri.
> > >
> >
> > --
> > Mark Nottingham https://www.mnot.net/
> >
>
>
Received on Monday, 21 September 2020 17:42:11 UTC