Re: Libraries assuming iso-8859-1 (was: Re: Consensus call to include Display Strings in draft-ietf-httpbis-sfbis)

• From: Julian Reschke <julian.reschke@gmx.de>
• Date: Sun, 28 May 2023 10:49:30 +0200
• To: ietf-http-wg@w3.org
• Message-ID: <23355080-503c-90ae-0961-a5197566dfe9@gmx.de>

On 28.05.2023 08:44, Martin J. Dürst wrote:
> ...
> There may also be implementations that just cut off the most significant
> bit in each byte, or otherwise don't let non-ASCII bytes through. It
> would be good to know whether such cases actually have been reported, or
> whether that's just something we think might be out there but isn't
> actually confirmed.
> ...

Historically (before RFC5987), Content-Disposition/filename was sent to
*some* browsers (Webkit, Chromium) using raw ISO-8899-x and/or UTF-8
(and sniffing the encoding). This apparently worked good enough so that
it took a huge amount of lobbying to get the UA implementers to agree to
uniformly support RFC 5987.

So at that point (~10 years ago), support for obs-text was apparently
"good enough" to use in practice.

Best regards, Julian

Received on Sunday, 28 May 2023 08:49:38 UTC