"New" SSL - a problem (which could be mine) and a suggestion

[Steve Davis]

Hi Dan and anyone following this,

So it turns out this issue is caused by a badly behaved browser -
Google Chrome. The issue doesn't surface with Firefox.

Right now it seemms that Chrome is being handed a client socket that
it is (for some reason) closing out on immediately.

I'll do some investigation with wireshark to find out exactly what's
going on - it looks like a browser bug right now.

/sd

On Aug 18, 4:28 am, Steve Davis <steven.charles.da...@REDACTED>
wrote:
> Thanks, Dan -
>
> I'll spend time with it soon as I can get to it to make sure it's "not
> just me" and get some repro code across to erlang-bugs - I'll let you
> know either way.
>
> Best regards,
> Steve
>
> Dan Gudmundsson wrote:
> > No not a known issue, any help/debug-able example would be great.
>
> > /Dan
>
> ________________________________________________________________
> erlang-questions mailing list. Seehttp://www.erlang.org/faq.html
> erlang-questions (at) erlang.org