Opening a socket over SSL

[wwwyaron]

Hi,

Library is working very well over a WS connection.

Is there a way to configure a secure connection over SSL, with WSS?

Thanks!
Yaron

[dhtml]

Hmn, I have not tried that yet. Did you test it over SSL or WSS and have
an error?

On 9/14/2016 10:48 PM, wwwyaron wrote:

Hi,

Library is working very well over a WS connection.

Is there a way to configure a secure connection over SSL, with WSS?

Thanks!
Yaron

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA53hF0r3cac3ohAzgQcvKLQTSP0qAS6ks5qqGuTgaJpZM4J9R-T.

Tony Ogundipe *| Programming Head
*
*Information & Communications Technology
*cell: +234 (0) 703 029 0746, 0812 075 5515
*Skype: diltony

DISCLAIMER: This email and any attachment transmitted with it are
confidential and intended solely for the use of the individual or entity
to which it is addressed. If yo
​​
u happen to have received this email in error, please delete this email
from your system and notify the sender immediately by email. If you have
received this email by mistake, note that disseminating, distributing,
copying, printing, disclosing its contents or taking any action in
reliance on the contents of this email is strictly prohibited. Although
_/Bytes /_has taken reasonable precautions to ensure that no viruses are
present in this email and any attachment transmitted with it, /Bytes /
will not accept liability for any damage or loss caused by any virus
transmitted by this email. Emails cannot be guaranteed to be secure or
error free as the message and any attachments transmitted with it could
be intercepted, corrupted, lost, delayed, incomplete or amended.
Therefore, /Bytes / and the sender do not accept liability for any
errors or omissions in the contents of this message, which arise as a
result of email transmission. /Bytes / accepts no liability for the
content of this email or for the consequences of any actions taken on
the basis of the information provided, unless that information is
subsequently confirmed in writing.
*
*
*
*
*
*
Tony Ogundipe *| Programming Head
*
*Information & Communications Technology
*cell: +234 (0) 703 029 0746, 0818 643 6222
*Skype: diltony

DISCLAIMER: This email and any attachment transmitted with it are
confidential and intended solely for the use of the individual or entity
to which it is addressed. If yo
​​
u happen to have received this email in error, please delete this email
from your system and notify the sender immediately by email. If you have
received this email by mistake, note that disseminating, distributing,
copying, printing, disclosing its contents or taking any action in
reliance on the contents of this email is strictly prohibited. Although
_/Bytes /_has taken reasonable precautions to ensure that no viruses are
present in this email and any attachment transmitted with it, /Bytes /
will not accept liability for any damage or loss caused by any virus
transmitted by this email. Emails cannot be guaranteed to be secure or
error free as the message and any attachments transmitted with it could
be intercepted, corrupted, lost, delayed, incomplete or amended.
Therefore, /Bytes / and the sender do not accept liability for any
errors or omissions in the contents of this message, which arise as a
result of email transmission. /Bytes / accepts no liability for the
content of this email or for the consequences of any actions taken on
the basis of the information provided, unless that information is
subsequently confirmed in writing.

[wwwyaron]

I have, connection cannot be established.
Just to clarify - connection to the web server over standard https/443 works well.
Seems like the websocket server doesn't bind the WS port to a certificate.

[dhtml]

Hmn, I seem not have any workaround for this at the moment.

On 9/15/2016 4:37 PM, wwwyaron wrote:

I have, connection cannot be established.
Just to clarify - connection to the web server over standard https/443
works well.
Seems like the websocket server doesn't bind the WS port to a certificate.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#2 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA53hMifzwgzLVI-VzM-qI-DtSDJ9aBXks5qqWZAgaJpZM4J9R-T.

Tony Ogundipe *| Programming Head
*
*Information & Communications Technology
*cell: +234 (0) 703 029 0746, 0812 075 5515
*Skype: diltony

DISCLAIMER: This email and any attachment transmitted with it are
confidential and intended solely for the use of the individual or entity
to which it is addressed. If yo
​​
u happen to have received this email in error, please delete this email
from your system and notify the sender immediately by email. If you have
received this email by mistake, note that disseminating, distributing,
copying, printing, disclosing its contents or taking any action in
reliance on the contents of this email is strictly prohibited. Although
_/Bytes /_has taken reasonable precautions to ensure that no viruses are
present in this email and any attachment transmitted with it, /Bytes /
will not accept liability for any damage or loss caused by any virus
transmitted by this email. Emails cannot be guaranteed to be secure or
error free as the message and any attachments transmitted with it could
be intercepted, corrupted, lost, delayed, incomplete or amended.
Therefore, /Bytes / and the sender do not accept liability for any
errors or omissions in the contents of this message, which arise as a
result of email transmission. /Bytes / accepts no liability for the
content of this email or for the consequences of any actions taken on
the basis of the information provided, unless that information is
subsequently confirmed in writing.
*
*
*
*
*
*
Tony Ogundipe *| Programming Head
*
*Information & Communications Technology
*cell: +234 (0) 703 029 0746, 0818 643 6222
*Skype: diltony

DISCLAIMER: This email and any attachment transmitted with it are
confidential and intended solely for the use of the individual or entity
to which it is addressed. If yo
​​
u happen to have received this email in error, please delete this email
from your system and notify the sender immediately by email. If you have
received this email by mistake, note that disseminating, distributing,
copying, printing, disclosing its contents or taking any action in
reliance on the contents of this email is strictly prohibited. Although
_/Bytes /_has taken reasonable precautions to ensure that no viruses are
present in this email and any attachment transmitted with it, /Bytes /
will not accept liability for any damage or loss caused by any virus
transmitted by this email. Emails cannot be guaranteed to be secure or
error free as the message and any attachments transmitted with it could
be intercepted, corrupted, lost, delayed, incomplete or amended.
Therefore, /Bytes / and the sender do not accept liability for any
errors or omissions in the contents of this message, which arise as a
result of email transmission. /Bytes / accepts no liability for the
content of this email or for the consequences of any actions taken on
the basis of the information provided, unless that information is
subsequently confirmed in writing.