Switch http_parser to llhttp

[socketpair]

Nodejs decide to move from their hard-coded C parser to this one.

nodejs/http-parser#285 (comment)

Upd:
proposed parser is https://llhttp.org

[aio-libs-bot]

GitMate.io thinks the contributor most likely able to help you is @asvetlov.

Possibly related issues are #33 (HTTPS Support), #390 (404 on http://aiohttp.readthedocs.org/en/v0.16.3/), #320 (HTTP/2 support), #72 (HTTP POST not working), and #858 (replace http parser?).

[samuelcolvin]

Seems too good to be true, but must be worth trying.

Might be worth putting the link in the body of the issue so it's rendered as a link.

[socketpair]

https://llhttp.org

[asvetlov]

It worth to try.
API seems the same but I expect complications of our build process.
Don't have any personal estimation of the issue:

1. It would be nice to have but not urgent, existing parser just works
2. I have a long list of higher priority items in my todo list

[socketpair]

Interesting, suricata decide to write their own HTTP-parser on Rust :) https://redmine.openinfosecfoundation.org/issues/2787#change-10814

[derlih]

I found a problem with this port to llhttp: there is no API in llhttp that parses url.
These functions are needed by cdef class HttpRequestParser(HttpParser)
Does anyone have an idea how to workaround it?

my llhttp branch

[asvetlov]

They are not required I guess, yarl.URL can be constructed directly as we do for pure-Python parser.

[derlih]

@socketpair
I saw this project, but

This project is a toy, started to reacquaint myself with Python c-api modules.

[socketpair]

@derlih That's why I removed the link :) before your comment.

[socketpair]

https://github.com/pallas/pyllhttp