Okay, it's definitely something at the polarssl level. I was able to replicate the issue simply with one of polarssl's own tests. I've reported here:
https://github.com/polarssl/polarssl/issues/30 Could very well be a bug in Chrome, too. But at this point it seems Mongrel2 itself is in the clear. On Fri, Sep 13, 2013 at 2:55 AM, Justin Karneges <[email protected]> wrote: > I'm testing with Chrome 29 on Linux and it fails to connect to Mongrel2 > using https. The message from Chrome isn't very helpful: > > ----- > SSL connection error > > Unable to make a secure connection to the server. This may be a problem > with the server, or it may be requiring a client authentication certificate > that you don't have. > > Error code: ERR_SSL_PROTOCOL_ERROR > ----- > > Has anyone else seen this? Chrome 29 on Mac works just fine, so this is > Linux-specific. However, other stuff on the same Linux machine work fine > (FF23, Curl 7.27). IE10 also fine. > > Perhaps a very obscure PolarSSL incompatibility somewhere. Tomorrow I'll > go tcpdumping. > > Justin > -- Justin Karneges Fanout, Inc. 530-220-7222
