"RokuMarkn" wrote:
Actually it has been pointed out to me that RFC 3986 supersedes 1738, and it changes tilde to an unreserved character. So I think the current behavior is correct, and the tildes in the URL don't need to be encoded.
--Mark
Yes, it does look like UrlEncode () and Escape () both encode according to RFC 3986, in which case the bug would apply to the SDK documentation. The documentation states that Escape () will "URL encode the specified string using CURL" and that UrlEncode () uses an "Alternate URL encoding scheme with stricter RFC 1738 compliance". It appears that they both do the same thing, which is to encode according to RFC 3986.
I don't think any of this helps ShifterFilms with his problem, since none of the characters in the url he gave would require encoding, according to RFC 3986, although I agree that it's a good idea in general to encode parameters in the url query string.