Thank you very much. It's useful.
On Jun 18, 2:09 am, Felix Oldenburg oldenburg.fe...@googlemail.com
wrote:
I had the same issue with the ~ encoding. If ~ gets encoded to %7E the
signature is wrong, but with a plain ~ it's fine.
But if u look at abraham's php twitter library, which also
Thank you！
On Jun 18, 2:18 am, Abraham Williams 4bra...@gmail.com wrote:
Characters in the unreserved character set as defined by RFC3986 (ALPHA,
DIGIT, -, ., _, ~) MUST NOT be encoded.
http://tools.ietf.org/html/rfc5849#section-3.6
Abraham
-
Abraham Williams | InboxQ
Thank you for your reply.
But as I said, if encode ~, signature will be wrong.
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
There might be some other problem in u r signature generation.
but not about the ~ url encoding.
//kamesh
On Fri, Jun 17, 2011 at 1:57 PM, LoVenus pzunderta...@hotmail.com wrote:
Thank you for your reply.
But as I said, if encode ~, signature will be wrong.
--
Twitter developer
I had the same issue with the ~ encoding. If ~ gets encoded to %7E the
signature is wrong, but with a plain ~ it's fine.
But if u look at abraham's php twitter library, which also implements
the needed oauth functionality, u can see he also uses the non encoded
~.
(
