I couldn't view the bug, so I opened a new one:
http://code.google.com/p/chromium/issues/detail?id=129568
From my testing, it appears that requesting client authentication triggers
the bug. So perhaps we should only do the
sslContextFactory.setWantClientAuth(true)
if "enable_clientauth = true", to avoid triggering this when client auth
isn't being used.
On 2012-05-18 16:00, Thomas Leonard wrote:
Is this bug report secret for some reason? I get a 403 error trying to
access it.
On 2012-05-16 19:23, Ali Lown wrote:
I was wondering why I was having issues get the SSL Client-Auth code
to work locally correctly:
Chrome 19+ is broken with wss:// at the moment.
See http://code.google.com/p/chromium/issues/detail?id=128339
I can confirm the same problem with Chromium 20.0.1115.1
@Yuri: this is just a by-the-by in case someone reports it not
working, and so we know it isn't something we did.
Ali
--
Dr Thomas Leonard
IT Innovation Centre
Gamma House, Enterprise Road,
Southampton SO16 7NS, UK
tel: +44 23 8059 8866
mailto:[email protected]
http://www.it-innovation.soton.ac.uk/