What libraries we need
Lassi Kortela
(07 Apr 2019 08:55 UTC)
|
Re: What libraries we need
Peter Bex
(07 Apr 2019 09:31 UTC)
|
URI/URL handling
Lassi Kortela
(07 Apr 2019 10:11 UTC)
|
Re: URI/URL handling
Peter Bex
(07 Apr 2019 10:56 UTC)
|
Re: URI/URL handling
Lassi Kortela
(07 Apr 2019 12:03 UTC)
|
Re: URI/URL handling
Lassi Kortela
(07 Apr 2019 12:46 UTC)
|
Re: URI/URL handling
Peter Bex
(07 Apr 2019 14:20 UTC)
|
Re: URI/URL handling
Lassi Kortela
(07 Apr 2019 15:06 UTC)
|
Re: URI/URL handling
Peter Bex
(07 Apr 2019 15:39 UTC)
|
Re: URI/URL handling
Lassi Kortela
(07 Apr 2019 15:52 UTC)
|
Re: URI/URL handling
Peter Bex
(07 Apr 2019 16:03 UTC)
|
Re: URI/URL handling
Lassi Kortela
(07 Apr 2019 16:30 UTC)
|
Re: URI/URL handling Arthur A. Gleckler (09 Apr 2019 21:06 UTC)
|
Re: What libraries we need
Arthur A. Gleckler
(09 Apr 2019 20:49 UTC)
|
Peter Bex <xxxxxx@more-magic.net> writes: | Also note that encoding of query strings is a whole topic unto itself. The W3C recommendation (in the HTML spec!) is that & is no longer used to separate query arguments. Instead, servers should use ;. The reasons behind that are pretty inane (because apparently for many people it's too hard to get the & encoding right inside HTML), but the reality is that now many servers accept both & and ;, some still only accept & and there are probably servers that only accept ; too. Search the URI-common code [1] for "application/x-www-form-urlencoded" for the gory details. Wow, I wasn't aware of this. I implemented Shuttle's decoding based on the URI spec at the time, and I've never looked at it again. It's good to have an expert in the discussion.