Subject: Re: bug#24117: 25.1; url-http-create-request: Multibyte text in HTTP request

From: Lars Ingebrigtsen <[email-masked]>
Date: Mon, 08 Aug 2016 18:18:18 +0200

Eli Zaretskii <[email-masked]> writes:

>> It's be sad if
>> 
>> (url-generic-parse-url "http://góogle.com/fóo")
>> 
>> stopped working.
>
> It's already broken, because that function does nothing special for
> non-ASCII characters, although the corresponding RFC says they are not
> allowed.

No, it does what users expect it to.

(url-generic-parse-url "http://góogle.com/fóo")
=> [cl-struct-url "http" nil nil "góogle.com" nil "/fóo" nil nil t nil t]

"Aha, so 'góogle.com' is the domain name."

That you have to encode the data returned before doing network stuff
(which is what the RFC talks about) is a completely different matter.

The function is used to decompose URLs found in nature.  Those URLs
contain non-ASCII characters.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no