Re: Invalid Characters in URLs from Tim Bray on 2024-09-20 (ietf-http-wg@w3.org from July to September 2024)

From: Tim Bray <tbray@textuality.com>
Date: Fri, 20 Sep 2024 08:17:18 -0700
To: Daniel Stenberg <daniel@haxx.se>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, Biren Roy <birenroy@google.com>, Ryan Hamilton <rch@google.com>
Message-ID: <CAHBU6iu=7JYzVKxxzYbMxeLR=T0i_gZ-xLfK8rKHS6eGGuLibw@mail.gmail.com>

 AFAIK browsers, whatever WHAT iteration they follow, will correctly
interoperate on 3986-conforming URLs, no?  So protocol implementors should
expect to get good results if they stick with that?

WHAT’s strength (or weakness, according to some) is its very precise
specification of browser behavior in the presence of various flavors of
error.

-T

Received on Friday, 20 September 2024 15:17:24 UTC