十年前的 APMServ 今天的 PHPTS

暈死了，搞了quic那麽久一直沒有測試成功，最後才發現原來是goyoubbs程序使用的不是quic協議

而caddy只是代理，所以一直沒有成功，我的理解對嗎？

@waiducom #1 caddy 支持 quic

貌似这样 caddy -agree -quic 没用

@youbbs #3 嗯。却是是使用 -quic启动 。可能是。但是检查显示caddy是监听udp 443端口的。但是监听的却是IP v6。浏览器开发者工具显示却是没有使用quic. 而是HTTP2。可能是caddy的bug

@root #4 caddy 1 已弃用 quic 实验，将在 caddy 2 中支持。刚才去试了一下 caddy 2 搞了半天配置，各种错误。

2020/03/10 03:32:52.890	INFO	admin	admin endpoint started	{"address": "localhost:2019", "enforce_origin": false, "origins": ["localhost:2019"]}
2020/03/10 03:32:52.890	INFO	serving initial configuration

# ./caddy2_beta15_linux_amd64 run
2020/03/10 03:33:51.718	INFO	using adjacent Caddyfile
run: adapting config using caddyfile: unrecognized parameter name: apps

最后勉强运行了

# ./caddy2_beta15_linux_amd64 run
2020/03/10 03:44:00.324	INFO	using adjacent Caddyfile
2020/03/10 03:44:00.329	INFO	admin	admin endpoint started	{"address": "localhost:2019", "enforce_origin": false, "origins": ["localhost:2019"]}
2020/03/10 03:44:00.329	INFO	http	server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS	{"server_name": "srv0", "https_port": 443}
2020/03/10 03:44:00.330	INFO	http	enabling automatic HTTP->HTTPS redirects	{"server_name": "srv0"}
2020/03/10 03:44:00.330	INFO	http	enabling automatic TLS certificate management	{"domains": ["example.com", "www.example.com"]}
2020/03/10 03:44:00.331	INFO	tls	cleaned up storage units
2020/03/10 03:44:00.331	INFO	autosaved config	{"file": "/root/.config/caddy/autosave.json"}
2020/03/10 03:44:00.332	INFO	serving initial configuration
2020/03/09 23:44:00 [INFO][cache:0xc0006df4a0] Started certificate maintenance routine

也没看到 quic 协议，可能配置没有默认开启，不想再去折腾了，原来就图 caddy 配置方便，随着功能的增加 caddy 2 配置越来越复杂了。

@youbbs #5 确实是，caddy 感觉要凉了 我也是折腾了两天都没搞好。我觉得还不如在goyoubbs HTTP2 嵌入quic 省事 哈哈