From: Lars Ingebrigtsen <larsi@gnus.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 31248@debbugs.gnu.org
Subject: bug#31248: 27.0.50; Regression: Multibyte text in HTTP request
Date: Mon, 23 Apr 2018 19:04:53 +0200 [thread overview]
Message-ID: <m3604hrgzu.fsf@gnus.org> (raw)
In-Reply-To: <m2tvs1j3nv.fsf@gmail.com> (Aaron Jensen's message of "Mon, 23 Apr 2018 09:20:04 -0700")
Aaron Jensen <aaronjensen@gmail.com> writes:
> Before that, request with multi-byte characters in them were successful.
> Afterwards, they get the error:
>
> error in process sentinel: url-http-create-request: Multibyte text in
> HTTP request: POST /repos/user/repo/pulls HTTP/1.1
Is the multibyte text in the headers or in the POST? There's nothing
that looks multibytey in the headers of the HTTP request you included,
but the body looked suspicious. However, that commit doesn't seem to
affect the body at all, so I'm not sure how that commit could lead to a
regression in the POST body...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2018-04-23 17:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 16:20 bug#31248: 27.0.50; Regression: Multibyte text in HTTP request Aaron Jensen
2018-04-23 17:04 ` Lars Ingebrigtsen [this message]
2018-04-23 17:14 ` Aaron Jensen
2018-04-23 18:55 ` Lars Ingebrigtsen
2018-04-23 19:00 ` Aaron Jensen
2018-04-23 19:14 ` Lars Ingebrigtsen
2018-04-23 19:39 ` Aaron Jensen
2018-04-23 19:42 ` Lars Ingebrigtsen
2018-04-23 19:47 ` Aaron Jensen
2018-04-23 19:54 ` Lars Ingebrigtsen
2018-04-24 0:47 ` Aaron Jensen
2018-04-24 7:19 ` Andreas Schwab
2018-04-24 11:21 ` Aaron Jensen
2018-04-24 11:54 ` Lars Ingebrigtsen
2018-04-24 12:06 ` Lars Ingebrigtsen
2018-04-24 12:10 ` Aaron Jensen
2018-04-24 12:17 ` Lars Ingebrigtsen
2018-04-24 12:23 ` Lars Ingebrigtsen
2018-04-24 12:31 ` Aaron Jensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3604hrgzu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=31248@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.