diff options
Diffstat (limited to 'archives/extend/2015-January/000484.html')
| -rw-r--r-- | archives/extend/2015-January/000484.html | 110 |
1 files changed, 110 insertions, 0 deletions
diff --git a/archives/extend/2015-January/000484.html b/archives/extend/2015-January/000484.html new file mode 100644 index 00000000..74425562 --- /dev/null +++ b/archives/extend/2015-January/000484.html @@ -0,0 +1,110 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] websocket over ssl + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20websocket%20over%20ssl&In-Reply-To=%3C54B12F6E.6000305%40bestmx.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <style type="text/css"> + pre { + white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */ + } + </style> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="000485.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] websocket over ssl</H1> + <B>e at bestmx.net</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20websocket%20over%20ssl&In-Reply-To=%3C54B12F6E.6000305%40bestmx.net%3E" + TITLE="[99s-extend] websocket over ssl">e at bestmx.net + </A><BR> + <I>Sat Jan 10 14:55:58 CET 2015</I> + <P><UL> + + <LI>Next message: <A HREF="000485.html">[99s-extend] websocket over ssl +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#484">[ date ]</a> + <a href="thread.html#484">[ thread ]</a> + <a href="subject.html#484">[ subject ]</a> + <a href="author.html#484">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello all. + +I am trying to alter my cowboy-based websocket server from plain to SSL +connection. +And I found out that I have failed to understand very basics of the +combination of WS and SSL. + +As far as i've understood the very nature of the WS it is a bit altered +http connection (i open the http connection first, and then i change its +status to WS) + +On the other hand the whole "HTTP story" could be wrapped into SSL, so +that SSL is an outer layer of data encoding (as seen transparent by an +application) + +thus, +if I open HTTPS connection (which implies SSL enveloping) and then alter +the connection status to WS, the whole "WS story" appears naturally +INSIDE THE PREVIOUSLY ESTABLISHED SSL CONNECTION. + +Is it true? + +In this regard i can hardly find a place in this world for the "WSS" +term, what does it stand for? + +Please, help me fit it in my head. + +However, i might be confusing some Client-Side entities, that are +involved in the process of starting up my WebSocket. + +I am using a Browser with JavaScript. + +The semantics of the very WebSocket.start() operation is not enough +clear to me. Please, do not laugh. + +when i do JS WebSocket.start() does it: +(a) opens an http connection and then alters it to WS +(b) alters the connection in the context of which the JS process is running +???? + +I'll be damned if the answer was lying on the surface of the internet! + +The third part of this ugly question is about cowboy actually. +How all these entities mentioned above do map into my_app.erl file? +what particular bits of cowboy's "configuration" (may i call this +particular piece of code a "setup" or "config"?) affect what aspects of +the connection initialization. + +well, i am afraid it could be put in a simpler way: +"Exactly When and Where the WSS story begins?" + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="000485.html">[99s-extend] websocket over ssl +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#484">[ date ]</a> + <a href="thread.html#484">[ thread ]</a> + <a href="subject.html#484">[ subject ]</a> + <a href="author.html#484">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> |