WeidiDeng

@mholt I did some experiments with registering custom network, it's too much trouble to be worth it. Every site block needs an explicit `bind` and that includes http port and...

@flokli So that means you're fine with mixing passing FD and current binding behavior? And since you will use `bind` explicitly, it's an error to bind to an non existent...

@flokli You can try it with a plugin for now, `xcaddy build --with github.com/WeidiDeng/caddy-socket-activation`. Let me know what you think.

Actually, that patch is no longer present in the latest version (udp sockets are reused using `SO_REUSEADDR` on unix). That patch does enable more aggressive optimization from [quic-go](https://github.com/quic-go/quic-go). I guess...

The problem is, I don't have access to VMs right now. You can send a temporary credentials to my email, or running [ttyd](https://github.com/tsl0922/ttyd) with `-t enableTrzsz=true` with a limited privileged...

It seems there is a problem with express sending the wrong `Content-Length` header. When copying response, it hit `EOF` before the number of bytes are read, causing the response to...

According to [rfc 8441](https://datatracker.ietf.org/doc/rfc8441/), websocket over h2 requires `SETTINGS_ENABLE_CONNECT_PROTOCOL` to be sent by h2 server, currently golang doesn't allow sending custom h2 settings. Also the method has been changed from...

By the way, `x/net/websocket` is discontinued. This should go to `x/net/http2` instead.

This actually will partly modify `reverse_proxy`'s handling of 101 response based on whether client is using http2 if it is ever implemented.

Related changes required [here](https://github.com/golang/net/blob/master/http2/server.go#L885) upstream.