[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug in url-retrieve-synchronously from url.el on redirect
From: |
Yuri Khan |
Subject: |
Re: Bug in url-retrieve-synchronously from url.el on redirect |
Date: |
Sat, 11 Jul 2020 02:37:50 +0700 |
On Sat, 11 Jul 2020 at 01:49, Yuri Khan <yuri.v.khan@gmail.com> wrote:
>
> On Sat, 11 Jul 2020 at 01:18, Daniele Nicolodi <daniele@grinta.net> wrote:
>
> > url-retrieve-synchronously fails to obey redirect responses if the
> > returned "Location" header contains spaces: it redirects to the URL
> > truncated to the first space. It seems that spaces in the Location
> > header value are allowed (at least ngnix produces headers like that).
>
> They are not, and you should report it as a bug against nginx. It
> should be percent-encoding the space. It should also be
> percent-encoding any non-ASCII characters.
Actually, I went along and reported it myself, with an example that
clearly demonstrates a bug in nginx:
https://trac.nginx.org/nginx/ticket/2016
- Bug in url-retrieve-synchronously from url.el on redirect, Daniele Nicolodi, 2020/07/10
- Re: Bug in url-retrieve-synchronously from url.el on redirect, Yuri Khan, 2020/07/10
- Re: Bug in url-retrieve-synchronously from url.el on redirect,
Yuri Khan <=
- Re: Bug in url-retrieve-synchronously from url.el on redirect, Daniele Nicolodi, 2020/07/10
- Re: Bug in url-retrieve-synchronously from url.el on redirect, Yuri Khan, 2020/07/10
- Re: Bug in url-retrieve-synchronously from url.el on redirect, Daniele Nicolodi, 2020/07/10
- Re: Bug in url-retrieve-synchronously from url.el on redirect, Daniele Nicolodi, 2020/07/10
- Re: Bug in url-retrieve-synchronously from url.el on redirect, chad, 2020/07/13
- Re: Bug in url-retrieve-synchronously from url.el on redirect, Daniele Nicolodi, 2020/07/13