From: Thomas Hisch <thomas.hisch@ims.co.at>
To: Andreas Schwab <schwab@suse.de>, Eli Zaretskii <eliz@gnu.org>
Cc: 34855@debbugs.gnu.org
Subject: bug#34855: 27.0.50; url-retrieve-synchronously Bad request Error every 2nd call
Date: Fri, 22 Mar 2019 21:13:32 +0100 [thread overview]
Message-ID: <f0ea4358-784c-188a-cba5-8bf34d018a51@ims.co.at> (raw)
In-Reply-To: <871s3326zy.fsf@igel.home>
On 3/18/19 10:43 PM, Andreas Schwab wrote:
> On Mär 14 2019, Eli Zaretskii <eliz@gnu.org> wrote:
>
>>> CC: <34855@debbugs.gnu.org>
>>> From: Thomas Hisch <thomas.hisch@ims.co.at>
>>> Date: Thu, 14 Mar 2019 17:48:24 +0100
>>>
>>> The commit that broke it is
>>>
>>> 84613dae5c34ea742dd9a3e56f5acb55f604b483
>>>
>>> Reverting it locally fixed the issue for me.
>>
>> Thanks. Andreas, could you please take a look at this?
>
> I'm not allowed to read his mails.
Do you mean mine?
(https://lists.gnu.org/archive/html/bug-gnu-emacs/2019-03/msg00404.html)
My company surprisingly switched to official (= non self-signed)
certificates last week. I've tested my testcode today again with the
latest HEAD of the master branch and I can no longer reproduce this issue.
I have no idea why the old self-signed certificates caused an issue that
is fixed by reverting 84613dae5c34ea742dd9a3e56f5acb55f604b483.
Regards
Thomas
next prev parent reply other threads:[~2019-03-22 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 11:01 bug#34855: 27.0.50; url-retrieve-synchronously Bad request Error every 2nd call Thomas Hisch
2019-03-14 12:38 ` Eli Zaretskii
2019-03-14 16:48 ` Thomas Hisch
2019-03-14 18:06 ` Eli Zaretskii
2019-03-18 21:43 ` Andreas Schwab
2019-03-22 20:13 ` Thomas Hisch [this message]
2019-03-22 21:00 ` Eli Zaretskii
2019-03-22 22:42 ` Thomas Hisch
2019-03-23 6:39 ` Eli Zaretskii
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=f0ea4358-784c-188a-cba5-8bf34d018a51@ims.co.at \
--to=thomas.hisch@ims.co.at \
--cc=34855@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@suse.de \
/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.