Le 23/09/2013 10:42, ianG a écrit :
And yes, once HTTPS is indicated on the original request, it has to
maintain SSL/TLS protection across the lot, otherwise the security
claim is broken.
That's not the case already, so there should not be an exception for
WebSockets.
In my case this
don't understand what you mean
exactly by already fixed up the other channel, the fact here is that
you connect to routers that can not have a trusted certificate).
Regards,
Aymeirc
Le 24/09/2013 09:38, ianG a écrit :
On 23/09/13 12:16 PM, Aymeric Vitte wrote:
Le 23/09/2013 10:42, ianG a écrit
: nicho...@nicholaswilson.me.uk
Site and blog: www.nicholaswilson.me.uk
28 St Stephens Place, CB3 0JE
07845 182898
On 23 September 2013 09:21, Aymeric Vitte vitteayme...@gmail.com wrote:
Please see: https://bugzilla.mozilla.org/show_bug.cgi?id=917829
I think I have detailed already in the bug report
I did not look again but as far as I remember the concepts of
convergence are not really applicable any longer, because they suppose
that there is a finite set of certificates used, and if you look at
sites like google, twitter, etc with some plugins to catch the
certificates, you will see
