W3C home > Mailing lists > Public > public-i18n-archive@w3.org > January to March 2017

[i18n-activity] Subscription request needs to define UTF-8

From: Addison Phillips via GitHub <sysbot+gh@w3.org>
Date: Mon, 13 Feb 2017 21:55:42 +0000
To: public-i18n-archive@w3.org
Message-ID: <issues.opened-207351089-1487022940-sysbot+gh@w3.org>
aphillips has just created a new issue for 

== Subscription request needs to define UTF-8 ==

In section 5.1, the subscription request is defined:

> Subscription is initiated by the subscriber making an HTTPS or HTTP 
POST [RFC7231] request to the hub URL. This request MUST have a 
Content-Type header of application/x-www-form-urlencoded (described in
 Section 17.13.4 of [W3C.REC-html401-19991224]) and the following 
parameters in its body, formatted accordingly:

URL Encoded does not define the character encoding used. Normally, the
 encoding is inferred from the sending page/URL. The specification 
should define the encoding explicitly to always be UTF-8.

Please view or discuss this issue at 
https://github.com/w3c/i18n-activity/issues/324 using your GitHub 
Received on Monday, 13 February 2017 21:55:51 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 18:09:36 UTC