/lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-July/027189.html
https://github.com/whatwg/whatwg.org · HTML · 117 lines · 65 code · 45 blank · 7 comment · 0 complexity · a24add20c9ad98b686387207251618eb MD5 · raw file
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
- <HTML>
- <HEAD>
- <TITLE> [whatwg] WebSocket restriction on the server's subprotocol
- </TITLE>
- <LINK REL="Index" HREF="index.html" >
- <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20WebSocket%20restriction%20on%20the%20server%27s%20subprotocol&In-Reply-To=%3Cop.vf4wjqakidj3kv%40dhcp-190.linkoping.osa%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="027188.html">
- <LINK REL="Next" HREF="027245.html">
- </HEAD>
- <BODY BGCOLOR="#ffffff">
- <H1>[whatwg] WebSocket restriction on the server's subprotocol</H1>
- <!--htdig_noindex-->
- <B>Simon Pieters</B>
- <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20WebSocket%20restriction%20on%20the%20server%27s%20subprotocol&In-Reply-To=%3Cop.vf4wjqakidj3kv%40dhcp-190.linkoping.osa%3E"
- TITLE="[whatwg] WebSocket restriction on the server's subprotocol">simonp at opera.com
- </A><BR>
- <I>Tue Jul 20 01:58:28 PDT 2010</I>
- <P><UL>
- <LI>Previous message: <A HREF="027188.html">[whatwg] Canvas: Rendering radial gradients beyond the terminal stops
- </A></li>
- <LI>Next message: <A HREF="027245.html">[whatwg] WebSockets feedback
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#27189">[ date ]</a>
- <a href="thread.html#27189">[ thread ]</a>
- <a href="subject.html#27189">[ subject ]</a>
- <a href="author.html#27189">[ author ]</a>
- </LI>
- </UL>
- <HR>
- <!--/htdig_noindex-->
- <!--beginarticle-->
- <PRE>The WebSocket spec restricts the value of the subprotocol that the client
- is allowed to send to the server (see step 3 in the WebSocket()
- constructor algorithm). However there's no restriction on the server side
- (see step 2 of Sending the server's opening handshake). The client could
- not have asked for any subprotocol, but the server can still respond with
- a subprotocol, and the connection will be accepted.
- Shouldn't the server have the same restriction as the client?
- --
- Simon Pieters
- Opera Software
- </PRE>
- <!--endarticle-->
- <!--htdig_noindex-->
- <HR>
- <P><UL>
- <!--threads-->
- <LI>Previous message: <A HREF="027188.html">[whatwg] Canvas: Rendering radial gradients beyond the terminal stops
- </A></li>
- <LI>Next message: <A HREF="027245.html">[whatwg] WebSockets feedback
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#27189">[ date ]</a>
- <a href="thread.html#27189">[ thread ]</a>
- <a href="subject.html#27189">[ subject ]</a>
- <a href="author.html#27189">[ author ]</a>
- </LI>
- </UL>
- <hr>
- <a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
- mailing list</a><br>
- <!--/htdig_noindex-->
- </body></html>