Indeed it is; I didn't read properly. I thought a more natural place would be Protocols.HTTP, but now when I check up the relevant rfc the encoding is actually part of the uri syntax rather than http. So instead I wonder why the function got named "http_encode_string" in the first place and not "uri_encode_string". So shouldn't it actually be Standards.URI.uri_encode?