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

From: Eli Zaretskii <[email-masked]>
Date: Mon, 08 Aug 2016 20:11:42 +0300

> From: Lars Ingebrigtsen <[email-masked]>
> Cc: [email-masked],  [email-masked],  [email-masked]
> Date: Mon, 08 Aug 2016 18:58:23 +0200
> 
> Eli Zaretskii <[email-masked]> writes:
> 
> >> (And it is perfectly valid for the domain bits of URLs to contain
> >> non-ASCII characters after the IDNA changeover in the RFCs.)
> >
> > They must be unibyte.
> 
> I have no idea what you mean.

What I said: the URL strings must be unibyte strings.  Then they will
still work in url-generic-parse-url, and the problems which started
this bug report won't happen.

> If we have an <a href="http://góogle.com/foo"> instance, we have to
> decompose the URL into the domain part (góogle.com) and the local part
> (/foo), and then connect to the domain part (after IDNA encoding) and
> issue "GET /foo".

You can do all that with unibyte strings.

> If the decomposition function barfs on the URL, then we can't make
> the connection.

No one intends to make that function barf.