Currently we do URL-encode each path component, and then RestClient encodes the full path, so "foo$bar" results in "foo%2524bar" instead of simply "foo%24bar". The only thing we should worry about when building paths is that characters that have a meaning in the path ('/' in particular) are escaped, but this escaping should be custom and can be lossy (we don't want the server to un-escape it anyway). |