No worries J at least your trying to help. I think the minimum must be TLS 1.0
because I know I didn’t set the tls server config value, however, I do know
exactly where to set it. I asked this question in the Go repo on Github, a core
golang developer told me to use the forums for asking questio
But what I don’t get is why SSL Labs test shows that we do indeed support TLS
1.0?
https://www.ssllabs.com/ssltest/analyze.html?d=einthusan.tv&latest
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop
Are you suggesting to set the minimum to 1.1? Wouldn't that cause less
compatibility? Maybe a typo in your reply?
Sent from iPhone
> On Dec 31, 2016, at 2:28 PM, Tamás Gulácsi wrote:
>
> No, but the Go default min is TLS1.0, not TLS1.1, that's why you need a
> custom TLSConfig!
>
> --
> You
>
> 2016. december 28., szerda 20:46:03 UTC+1 időpontban einthusan a
> következőt írta:
>>
>> I manage a site with very large traffic and using Go 1.8 beta in
>> production. We moved over from a PHP implementation by re-writing
>> everything from scratch in go. W
I manage a site with very large traffic and using Go 1.8 beta in
production. We moved over from a PHP implementation by re-writing
everything from scratch in go. We saw a significant drop in our users, and
seeing our logs flooding with http: TLS handshake error from ::
EOF errors. I am not sure
