[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: Daniele Nicolodi
Subject: Re: Bug in url-retrieve-synchronously from url.el on redirect
Date: Fri, 10 Jul 2020 14:32:37 -0600
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.9.0

On 10/07/2020 14:25, Yuri Khan wrote:
> On Sat, 11 Jul 2020 at 02:43, Daniele Nicolodi <daniele@grinta.net> wrote:
>> As far as I understand the RFCs (and being wrong before, I may be wrong
>> again) do not allow for < > quoting either. Why does url-http.el strip
>> them? Why does it break the URI at the first space if spaces are not
>> allowed?
> I cannot answer that, maybe someone who is knowledgeable about
> uri-http.el chimes in.
> RFC 7231 allows clients to attempt to DTRT with invalid Location URIs
> in any way they deem appropriate; you could argue for a different
> recovery heuristic. Me, I’d rather have things break loudly on each
> violation, so that it does not go unnoticed for too long. Postel’s
> Razor is how we got HTML in its current shape.

I tend to agree with you, but, in this specific case, being compatible
with other HTTP implementations is a worthwhile goal.

Unfortunately, re-defining url-http-parse-headers is the only
work-around I found to make Emacs do the less bad thing when dealing
with this malformed URIs.


reply via email to

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