Open
Description
From #1615, it looks like escape_url_query()
is not always suitable, since it replaces space with +
. We should consider exposing url.PathEscape()
as well. Not sure if escape_url_path()
is the right name for it, since, in some cases, one might want to apply it to the entire URL, I think... Maybe http_encode()
is a better name?
Or maybe users should first call the new parse_url()
method from cbf450e and encode each part individually?