- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Wed, 6 Jun 2012 15:34:21 +0200
- To: public-rww <public-rww@w3.org>
- Message-ID: <CAKaEYhKEvtPfjbesjCbbJQ56BRTMaHsVNaXh4AE8v5BNx_kv+g@mail.gmail.com>
FYI
---------- Forwarded message ----------
From: Nathan Rixham <nrixham@gmail.com>
Date: 6 June 2012 15:33
Subject: [Fwd: Re: Issue 63158 in chromium: secure websockets support for
client side certificates]
To: Melvin Carvalho <melvincarvalho@gmail.com>, Henry Story <
henry.story@gmail.com>
Good news, chromium devs just started working on cert support for
websockets :)
-------- Original Message --------
Subject: Re: Issue 63158 in chromium: secure websockets support for client
side certificates
Date: Wed, 06 Jun 2012 12:35:22 +0000
From: chromium@googlecode.com
To: nrixham@gmail.com
References: <9-17588020830446002922-**14064482877818702605-chromium=**
googlecode.com@googlecode.com <googlecode.com@googlecode.com>>
<0-17588020830446002922-**14064482877818702605-chromium=**
googlecode.com@googlecode.com <googlecode.com@googlecode.com>>
Updates:
Status: Started
Comment #10 on issue 63158 by toyos...@chromium.org: secure websockets
support for client side certificates
http://code.google.com/p/**chromium/issues/detail?id=**63158<http://code.google.com/p/chromium/issues/detail?id=63158>
(No comment was entered for this change.)
--
You received this message because you starred the issue.
You may adjust your notification preferences at:
https://code.google.com/**hosting/settings<https://code.google.com/hosting/settings>
Reply to this email to add a comment.
Received on Wednesday, 6 June 2012 13:34:56 UTC