hi, have you found the solution yet?
I trie matt.life in my chrome with no plug-ins, with quic enabled,
but when I access matt.life, it shows that it is run on HTTP2 protocol, not quic!
But when I access quictranfer.com, it actually shows that it is running quic.
So what is the problem really is ?
I run caddy with -quic in command line and the response header involve
alt-svc:quic=":443"; ma=2592000; v=“36,35,34”
alternate-protocol:443:quic
But I could only find it running HTTP2 with self-signed CA.
It works on my site now. To be honest i’m not really sure what fixed it. I sort of gave up on it, just decided to look into it later. Couple of days later I visited my website and noted it was running quic!
Maybe it’s as simple as restarting Caddy and Chrome? And did you enable the quic flag in chrome://flags?
localhost:443 {
tls CertificateGenerator/out/leaf_cert.pem CertificateGenerator/out/leaf_cert.key
root example
log access.log
}
my server and client are both on my computer.
I don’t understand if it is concerned with firewall/router? Or could you offer more details on how to open/forward port 443 UDP? Does it mean I should modify my caddyfile or I should change settings on my OS X 10.12.3?
Hmmm didn’t see you where testing your localhost. You are right that port forwarding isn’t necessary then. I’m a little bit out of options to be honest.
Did you build Caddy yourself or did you download it from the releases? QUIC isn’t working with current builds of master with golang 1.8. I captured it in a ticket here: https://github.com/mholt/caddy/issues/1483
Builds of the v0.9.5 tag with golang 1.7 should work for you, or the binary from the download server if you don’t care about POSTs over QUIC.