Re: [PATCH] url: Wrap cookie headers in url-http--encode-string.

[Alain Schneble]

Eli Zaretskii <address@hidden> writes:

> If you just generate an ASCII string from ASCII characters, it will
> usually be unibyte.  If you take it as a substring from a multibyte
> buffer, it will usually be multibyte.

Thanks for your patience.

> That's not the issue.  The issue is whether a cookie-value can
> legitimately have non-ASCII characters.  If it can, then we must
> _encode_ the cookie-value, as that is the only correct way of getting
> a unibyte string from non-ASCII characters.  And you pointed to an RFC
> that seems to say non-ASCII characters in cookies are possible.

Yes true, but I thought that maybe fixing this as described could be a
viable non-invasive alternative for the upcoming 25.1 release.