Tatsuhiro Tsujikawa

nghttpx ingress controller does not use nginx. I do not know which nginx ingress controller you are using, but you should ask its vendor or developers.

I use the following API functions to parse URLs: ```c /* Initialize all http_parser_url members to 0 */ void http_parser_url_init(struct http_parser_url *u); /* Parse a URL; return nonzero on failure...

I need all fields which http_parser_url has because original URL cannot be reconstructed from http_parser_url if there are any missing fields.

Perhaps, we can treat line starting with white space in input-file specially so that it can contain additional per URI parameter. This is just an idea, something like this: ```...

h2load has no option not to reuse existing connection.

h2load -v option would provide more verbose log. Not sure what happened there but it looks like h2load did not like something it got. Which server are you using?

Thanks. It seems that HTTP/3 (possibly QPACK) does not work well here.

So you have some troubles between unknown version lsquic and h2load. I haven't seen any problem so far with lsquic in the past, but will check and see which callbacks...

I guess that the stream was terminated in a way that ngtcp2 does not like and the entire connection was terminated. ngtcp2 client can show all received bytes, which might...

I normally develop nghttp2 on Debian, and so ubuntu should work too. Have you tried examples/asio-sv and examples/asio-sv2? They are asio examples. It looks like Debian/ubuntu boost is very sensitive...