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: Sun, 14 Jun 2020 09:49:04 -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="62955"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Dmitry Gutov , =?windows-1252?Q?I=F1igo?= Serna , Emacs developers To: Yuri Khan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 14 15:49:45 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 1jkT16-000GJh-Iu for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Jun 2020 15:49:44 +0200 Original-Received: from localhost ([::1]:56490 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jkT15-0004kq-KU for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Jun 2020 09:49:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55696) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jkT0b-0004Ld-2Q for emacs-devel@gnu.org; Sun, 14 Jun 2020 09:49:13 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:26694) by eggs.gnu.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jkT0Y-0006Sh-Tf for emacs-devel@gnu.org; Sun, 14 Jun 2020 09:49:12 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id C2B76100311; Sun, 14 Jun 2020 09:49:07 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 307831002FA; Sun, 14 Jun 2020 09:49:06 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1592142546; bh=BRLT/3SKuY9YccKH6XGA99imsH29ekXZQn2cZnrHcgg=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=MxfGlXiCAYyPle91ZTt+Teo3Cxc2alCofJZcOYNCsID6XxUXcM0SLcHhu3xmuUF8k jk0knEEZIE+uu+2TblmJcB0xCxZVSZNvTXojfse1iFl2W7Ic+mD4qL1fbPvt1WKMDc NJvmqc6MnfopvQVZxQnYzgwe4yun5p3jgaF26UtJxT+8hdd2nfQ8jhADXBEJo9KoVc 2gUU4hLhOOSOuOQj2MYy1VWjBJ4LV4QZHx7IjEDnaF3nezscnLnTbaGt7umuuFTqXU lQjc41LJXaRUMPti+oxyGCgJ0EB4qKKygtvTmZy7lRwlW3KYllRg7ANvJsG5q0R6b9 vFqnwqI5OiQqg== Original-Received: from alfajor (unknown [216.154.55.41]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id EAB771204BA; Sun, 14 Jun 2020 09:49:05 -0400 (EDT) In-Reply-To: (Yuri Khan's message of "Sun, 14 Jun 2020 15:33:04 +0700") 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/14 09:49:08 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:252230 Archived-At: >> 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. > > An application might not want to send the encoded string over the > network right away. It might want to insert it into a buffer. I didn't suggest to change the behavior, only to document it because both outputs can make sense, so common sense is not sufficient to know what should be returned. Stefan