Re: parsing URI (references) according to RFC 3986

On 2011-06-20 09:21, Adam Barth wrote:
> ...
> I wouldn't worry about file URLs for a while.  They're vastly more
> complex than all the other kinds of URLs put together.  If we could
> get interoperability for even just http URLs, I'd be happy.
> ...

+1

So, what *is* the set of interop problems here?

1) Extracting them from a/@href and friends (whitespace treatment)

2) Handling invalid ASCII characters (SP, "\", "<", ">"...)

3) Handling non-ASCII characters in query component

4) Handling non-ASCII characters in authority components

5) Handling non-ASCII characters everywhere else

Anything else?

Best regards, Julian

Received on Monday, 20 June 2011 07:38:27 UTC