Matthew Holt b4cab78bec Starting transition to Go 1.6 (http2 compatibility) ... I've built this on Go 1.6 beta 1 and made some changes to be more compatible. Namely, I removed the use of the /x/net/http2 package and let net/http enable h2 by default; updated the way h2 is disabled (if the user requires it); moved TLS_FALLBACK_SCSV to the front of the cipher suites list (all values not accepted by http2 must go after those allowed by it); removed the NextProto default of http/1.1; set the http.Server.TLSConfig value to the TLS config used by the listener (we left it nil before, but this prevents automatic enabling of h2). It is very likely there is more to do, but at least already Caddy uses HTTP/2 when built with Go 1.6.		2016-01-13 00:29:22 -07:00
..
config.go	letsencrypt: Major refactor of Activate(), fixes #474 and closes #397	2016-01-06 16:04:08 -07:00
config_test.go	Parser separate scheme/port, refactor config loading	2016-01-03 16:41:29 -07:00
graceful.go	Several improvements and bug fixes related to graceful reloads	2015-11-14 18:00:25 -07:00
server.go	Starting transition to Go 1.6 (http2 compatibility)	2016-01-13 00:29:22 -07:00
virtualhost.go	Moved fileServer and browse.IndexPages into middleware package	2015-09-19 20:35:48 -06:00