diff options
Diffstat (limited to 'archives/extend/2015-January/000488.html')
| -rw-r--r-- | archives/extend/2015-January/000488.html | 112 |
1 files changed, 112 insertions, 0 deletions
diff --git a/archives/extend/2015-January/000488.html b/archives/extend/2015-January/000488.html new file mode 100644 index 00000000..ada46131 --- /dev/null +++ b/archives/extend/2015-January/000488.html @@ -0,0 +1,112 @@ +<!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=%3CB264D9ED-5411-41D7-A481-1590E286DD74%40gmail.com%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="Previous" HREF="000490.html"> + <LINK REL="Next" HREF="000489.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] websocket over ssl</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20websocket%20over%20ssl&In-Reply-To=%3CB264D9ED-5411-41D7-A481-1590E286DD74%40gmail.com%3E" + TITLE="[99s-extend] websocket over ssl">lee.sylvester at gmail.com + </A><BR> + <I>Sat Jan 10 15:39:41 CET 2015</I> + <P><UL> + <LI>Previous message: <A HREF="000490.html">[99s-extend] websocket over ssl +</A></li> + <LI>Next message: <A HREF="000489.html">[99s-extend] websocket over ssl +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#488">[ date ]</a> + <a href="thread.html#488">[ thread ]</a> + <a href="subject.html#488">[ subject ]</a> + <a href="author.html#488">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>I use Cowboy for websockets, but I find it’s a lot easier (and less stressful) to run Nginx in front of it to provide the SSL layer. + +Lee + + +><i> On 10 Jan 2015, at 13:55, <A HREF="https://lists.ninenines.eu/listinfo/extend">e at bestmx.net</A> wrote: +</I>><i> +</I>><i> Hello all. +</I>><i> +</I>><i> I am trying to alter my cowboy-based websocket server from plain to SSL connection. +</I>><i> And I found out that I have failed to understand very basics of the combination of WS and SSL. +</I>><i> +</I>><i> 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) +</I>><i> +</I>><i> 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) +</I>><i> +</I>><i> thus, +</I>><i> 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. +</I>><i> +</I>><i> Is it true? +</I>><i> +</I>><i> In this regard i can hardly find a place in this world for the "WSS" term, what does it stand for? +</I>><i> +</I>><i> Please, help me fit it in my head. +</I>><i> +</I>><i> However, i might be confusing some Client-Side entities, that are involved in the process of starting up my WebSocket. +</I>><i> +</I>><i> I am using a Browser with JavaScript. +</I>><i> +</I>><i> The semantics of the very WebSocket.start() operation is not enough clear to me. Please, do not laugh. +</I>><i> +</I>><i> when i do JS WebSocket.start() does it: +</I>><i> (a) opens an http connection and then alters it to WS +</I>><i> (b) alters the connection in the context of which the JS process is running +</I>><i> ???? +</I>><i> +</I>><i> I'll be damned if the answer was lying on the surface of the internet! +</I>><i> +</I>><i> The third part of this ugly question is about cowboy actually. +</I>><i> How all these entities mentioned above do map into my_app.erl file? +</I>><i> 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. +</I>><i> +</I>><i> well, i am afraid it could be put in a simpler way: +</I>><i> "Exactly When and Where the WSS story begins?" +</I>><i> +</I>><i> _______________________________________________ +</I>><i> Extend mailing list +</I>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A> +</I>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">https://lists.ninenines.eu/listinfo/extend</A> +</I> +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000490.html">[99s-extend] websocket over ssl +</A></li> + <LI>Next message: <A HREF="000489.html">[99s-extend] websocket over ssl +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#488">[ date ]</a> + <a href="thread.html#488">[ thread ]</a> + <a href="subject.html#488">[ subject ]</a> + <a href="author.html#488">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> |