From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: url-retrieve "Multibyte text in HTTP request" error when passing UTF-8 Date: Sat, 13 Jun 2020 20:20:33 -0400 Message-ID: References: <87pna2eksc.fsf@inigo.katxi.org> <87mu56eehq.fsf@inigo.katxi.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="108667"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org, Dmitry Gutov To: =?windows-1252?Q?I=F1igo?= Serna Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 14 02:21:29 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jkGOv-000SC3-Cj for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Jun 2020 02:21:29 +0200 Original-Received: from localhost ([::1]:38040 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jkGOu-0004aO-B5 for ged-emacs-devel@m.gmane-mx.org; Sat, 13 Jun 2020 20:21:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39746) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jkGO9-0003YR-6P for emacs-devel@gnu.org; Sat, 13 Jun 2020 20:20:45 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:29809) by eggs.gnu.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jkGO6-0003qe-FE for emacs-devel@gnu.org; Sat, 13 Jun 2020 20:20:39 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 061A8441897; Sat, 13 Jun 2020 20:20:36 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id CA5154417F3; Sat, 13 Jun 2020 20:20:34 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1592094034; bh=1RuBTkw8YLhO2B9KP01fvHrT9rjZd55hi18+kxkCDH4=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=ObMTs4pThKI/H1WOIjcunOxQ8vUlG3AYKIp95f5A2HoZ+R2Fn4ZKI8xv9I/a73PXO DXiGrn8EfR2j9ngCDsi+j4CiFfZBGTobGR3nK2y+oh+v8i3FJ2A2n8gPYx3rhkHM/z bqzbaLxaXHaSVA4rBZ1YSeN7Fm4gWTvZI1ubqoRfiDR2OXodtOSNKpL+bkvZsmZiOE EnU+Ir71m0UcsPP8HwDIhSyUAYq+7CaeiO6ygZjaqCa5dBEvzVDQ9k11am0vJx4r2D wRFXG4WMfA7GuekHqIYRpMWfudRjcOJVQTyfJF4V2JdSmj4cyqx2kxyDXJCpKpanIk l1QaDGItoG5qQ== Original-Received: from alfajor (unknown [216.154.55.41]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 641AC12079C; Sat, 13 Jun 2020 20:20:34 -0400 (EDT) In-Reply-To: <87mu56eehq.fsf@inigo.katxi.org> (=?windows-1252?Q?=22I=F1igo?= Serna"'s message of "Sun, 14 Jun 2020 01:24:17 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/13 20:20:36 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:252220 Archived-At: > (url-request-data (encode-coding-string > (json-encode-alist `[(method . "slim.request") (params . [,playerid ,(split-string query)])]) > 'utf-8)) This might beg for some better documentation about the string returned by `json-encode`. After all, AFAIK the JSON format requires utf-8 encoding, so it would make a lot of sense for `json-encode` to do the utf-8 encoding directly and make sure it always returns a unibyte string. Stefan