I haven't had a chance to delve into this much yet, but for those of us who already have a "redirector" setup on port 80 to redirect ALL non-SSL traffic over to port 443 won't this introduce a problem? Or I suppose we could implement said redirection in the fallback handler, ditching the one we have?
regards, Paul On Sunday, 14 January 2018 22:49:39 UTC-8, alex wrote: > > If you use the autocert package, please update your code: you'll want to > add Manager.HTTPHandler[1] call to support "http-01" challenge type. > Unfortunately, this requires listening and accepting requests on port 80 > for the time being. See Manager example. > > Commit which adds "http-01" support to autocert.Manager: > > https://go.googlesource.com/crypto/+/13931e22f9e72ea58bb73048bc752b48c6d4d4ac > > This is due to TLS-SNI challenges being disabled now: > > https://community.letsencrypt.org/t/2018-01-11-update-regarding-acme-tls-sni-and-shared-hosting-infrastructure/50188 > > Sorry if this has already been posted. I couldn't find it. > > [1]https://godoc.org/golang.org/x/crypto/acme/autocert#Manager.HTTPHandler > . > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
