Thanks for investigating and opening this issue; I've starred it.

I notice it's been tagged as "Release-Go1.5". I very much hope that doesn't 
mean that we have to wait for Go 1.5 before there's a fix... :P

-r


On 11/10/2014 11:58 AM, David Birdsong wrote:
We use Heka to terminate TLS connections from our CDN and to parse their
syslog messages which get routed into our system, and I think you should
too.

We ran into a what appears to be a bug w/ Go crypto/tls which means our
deployment will require a work-around using other systems until it's fixed.

Take a look at this bug and if you don't mind, give it a vote to attract
attention it: https://code.google.com/p/go/issues/detail?id=9071


_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka


_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka

Reply via email to