Sergey Frolov

I did some manual testing, and it seems that popular browsers still generate a 32 byte SessionID, even when they don't have a ticket. The sessionID-less ClientHello you are trying...

That fork has plenty of valuable fixes and features, but, no, these fixes are not suitable to be merged upstream. The fork uses GPL, so, not only am I not...

Thanks for the report! I am not sure when I'll be able to dive into this issue, and PRs are always welcome. > When browse https://web.plus, caddy gives the vhost...

We could send all `CONNECT` requests into middleware chain with `forwardproxy`, but that doesn't integrate very well into current host matching logic of Caddy. As an aside, here's another temporary...

> Caddy should consider the SNI hostname Webservers generally don't do this, and there are setups that rely on this not being the case. Among other more general network configurations,...

I suspect this is a client-side issue. What client are you using? Does SwitchyOmega work for you?

@bash99 27401ebe3f2142da6436cae1f16c1f373e9a3f3e is not the latest commit, 05b2092e07f9d10b3803d8fb9775d2f87dc58590 is. Did you try it on both upstream and local? It involves a fix, that might be related to the issue you...

I cannot reproduce your issue with the latest build: it works for me. I used the same exact setup as you did with locahost upstreaming proxy on `:54086`

I dug deeper into this issue, but had no success discovering the cause. I suspect it gets compressed twice or `Content-Length` is not updated properly somewhere. @bash99 I will note,...

It appears to me that `gzip` writes header (which updates `Content-Length` and other things), only if header wasn't written [already](https://github.com/mholt/caddy/blob/master/caddyhttp/gzip/gzip.go#L135). Since the header is always written by the forwardproxy, gzip...