Hi,
here it is said that Error::TlsFail means we encountered problems during TLS handshake but this error is also returned by other functions e.g one that loads private key
https://github.com/cloudflare/quiche/blob/c726d349120ce72e8f0a00cd5176fd0767325511/src/lib.rs#L475

Will it be a good idea if TlsFail has message

The list of servers supporting QUIC mention only NGINX and Apache, but other servers support QUIC already.

• Caddy 0.9 had experimental support and Caddy 2.0 (currently beta) supports QUIC
  • https://github.com/caddyserver/caddy/wiki/QUIC
  • https://caddyserver.com (section "Web Protocols")
• When writing web services in G

While looking at the code, I noticed there are several failure paths in the QuicPacketBuilderFinalize function that don't result in the current packet metadata being cleaned up. It could have a reference to a stream, which doesn't get released. This will at best leak additional memory, and at worst cause a hang in clean up.

We currently issue flow control credit immediately upon application-layer consumption of data. This is excessive; we could slightly reduce overhead by instead issuing flow control credit when the amount that would be issued is at least a certain proportion of the entire window.

On the FOSS server fossies.org I have used a new functionality and have done as a trial a "codespell" run for the "lsquic" project. Here the version independent URL of the resulting report:

https://fossies.org/linux/www/lsquic/codespell.html

That URL redirects always to the URL of the report for the last "lsquic" release supported on Fossies (in case such a report was requested respectively

On the advice of a rep from the GoLiteSpeed slack channel I am logging this.

Whenever you setup an external app and configure a proxy, OLS seems to fill up the server error.log with request headers. If you have an app that constantly refreshes web sockets for data multiple times every few seconds then the log file amasses thousands of request headers every hour. It doesn't matter if you setup a

There should 0 new lint errors after migration

@HyundongHwang

example/MyStelliteTest project is test program for android system.

But project is name is not valid for android.

Would you modify this project name?
If you want more information to project name, please change appropirate name.

thank you.

I've changed my local version to:

public QuicStreamContext CreateStream(ulong streamId = 1, StreamType streamType = StreamType.ClientBidirectional);

in order to keep the compatibility.