I read the WRAP draft. I have to say that it's much simpler than OAuth 1.0a. It doesn't need too much modification to twitter client to support API proxy, if xauth is widely available.
Thank you all for your replies and concerns :-) On Feb 12, 7:04 pm, yegle <cnye...@gmail.com> wrote: > Oh yes I forgot that HTTP proxy resolves the domain name at server > side :-) > > On Feb 12, 6:18 pm, Harshad RJ <harshad...@gmail.com> wrote: > > > > > > > > > On Fri, Feb 12, 2010 at 12:17 PM, yegle <cnye...@gmail.com> wrote: > > > Nope, it doesn't work :-( > > > All DNS queries to twitter.com inside China is poisoned and all > > > twitter's available IP is blocked. > > > Oh btw, I meant HTTPS proxies that sit outside the firewall. > > > I assume that DNS queries for twitter.com would be run by the proxy server > > and not the client. (Tried to RTFM but still not very familiar with the > > protocol) > > > -- > > Harshad RJhttp://hrj.wikidot.com