[Top][All Lists]

[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 01:49:49 +0700

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.

The Location header is defined in RFC 7231, section 7.1.2, with a
value of URI-reference as defined in RFC 3986. The complete BNF
grammar is listed in Appendix A, and none of the productions there
contain the raw space character, nor raw non-ASCII characters.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]