Hi Taylor, well after much reading and reading and reading I’m in this situation:
- first: about you say of "configure my webserver to understand that “%28”, I don’t know if is possible to do it, I was looking for information about this but got nothing
- Second: I have no option to change the path 'cause it is a dynamic URL that is generated by the registered user and other directories
Finally, I was reading an oauth guide from “http://vimeo.com/api/docs/oauth” and found this in the section “Encoding”:
You’ll need to percent encode all of your parameters when creating your signature. These “reserved” characters must be converted into their hexadecimal values and preceded by a % character. The rest of the characters are “unreserved” and must not be encoded.
The reserved characters are:
! * ’ ( ) ; : @ & = + $ , / ? % # [ ]
These are the percent-encoded values of the above characters:
%21 %2A %27 %28 %29 %3B %3A %40 %26 %3D %2B %24 %2C %2F %3F %25 %23 %5B %5D
Unreserved characters include upper- and lower-case letters A through Z, numbers 0 through 0, and the dash, underscore, period, and tilde.
Be careful with URL encoding functions built into languages, they may not encode all of the reserved characters, or may encode unreserved characters.
After reading that, I think the encoding I’m doing is okay! and maybe the problem is the way I’m opening the window for authorization, because I’m doing it with a window.open like this:
what do you think?