/lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-December/066625.html
https://github.com/whatwg/whatwg.org · HTML · 85 lines · 73 code · 5 blank · 7 comment · 0 complexity · ffafa59179d43d181afa10e59756b9cc MD5 · raw file
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
- <HTML>
- <HEAD>
- <TITLE> [whatwg] WebSocket sub protocol name.
- </TITLE>
- <LINK REL="Index" HREF="index.html" >
- <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20WebSocket%20sub%20protocol%20name.&In-Reply-To=%3C4B1CC0C4.6050700%40gmx.de%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="066624.html">
- <LINK REL="Next" HREF="066626.html">
- </HEAD>
- <BODY BGCOLOR="#ffffff">
- <H1>[whatwg] WebSocket sub protocol name.</H1>
- <!--htdig_noindex-->
- <B>Julian Reschke</B>
- <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20WebSocket%20sub%20protocol%20name.&In-Reply-To=%3C4B1CC0C4.6050700%40gmx.de%3E"
- TITLE="[whatwg] WebSocket sub protocol name.">julian.reschke at gmx.de
- </A><BR>
- <I>Mon Dec 7 00:45:56 PST 2009</I>
- <P><UL>
- <LI>Previous message: <A HREF="066624.html">[whatwg] WebSocket sub protocol name.
- </A></li>
- <LI>Next message: <A HREF="066626.html">[whatwg] WebSocket sub protocol name.
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#66625">[ date ]</a>
- <a href="thread.html#66625">[ thread ]</a>
- <a href="subject.html#66625">[ subject ]</a>
- <a href="author.html#66625">[ author ]</a>
- </LI>
- </UL>
- <HR>
- <!--/htdig_noindex-->
- <!--beginarticle-->
- <PRE>Ian Hickson wrote:
- ><i> ...
- </I>>><i> And, why is it limited to ASCII instead of UTF-8?
- </I>><i>
- </I>><i> Because the HTTP working group refuse to allow UTF-8 in HTTP headers for
- </I>><i> reasons that I don't really understand, and the handshake is supposed to
- </I>><i> be valid HTTP.
- </I>><i> ...
- </I>
- A change of the default encoding would be incompatible with HTTP/1.1.
- ><i> On Mon, 7 Dec 2009, Julian Reschke wrote:
- </I>>><i> There isn't a good reason to disallow control characters in a *name*????
- </I>><i>
- </I>><i> Not as far as I can tell, no... what would a good reason be?
- </I>
- Consistency with every other single spec on the planet with respect to
- names?
- Best regards, Julian
- </PRE>
- <!--endarticle-->
- <!--htdig_noindex-->
- <HR>
- <P><UL>
- <!--threads-->
- <LI>Previous message: <A HREF="066624.html">[whatwg] WebSocket sub protocol name.
- </A></li>
- <LI>Next message: <A HREF="066626.html">[whatwg] WebSocket sub protocol name.
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#66625">[ date ]</a>
- <a href="thread.html#66625">[ thread ]</a>
- <a href="subject.html#66625">[ subject ]</a>
- <a href="author.html#66625">[ 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>