Why is so difficult to get answered now, and when u had the google groups was fast?


Hi I dont know if it is the right place, but, I am having big problems to resolve one issue with the oauth verification of my application (it was running for more than a year), the point is since 1 week ago, i am having big problems to get the request token, i checked and after some 401 errors generated by some changes from your side, the process is getting a 200 code (ok) but instead of receiving the request token, i receive an strange string (i havent deciphered!), My app is ASP classic,i checked it with http (original) and (https the same result), GET and POST the same.
Attached the log of the run : (Because no percentage permited here I replace it with X)

MSL in use Msxml2.ServerXMLHTTP.6.0
Host https://api.twitter.com
Authorization OAuth oauth_callback=“httpX3AX2FX2Fwww.quenota.comX2FauthX2Ftwitterqueno.asp”, oauth_consumer_key=“xxxxxx”, oauth_nonce=“hola251574”, oauth_signature=“yyyyyyyyyyy”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1355017844”, oauth_token="", oauth_version=“1.0”

Status 200


if you want to watch the string just replace X by percentage and urldecode it.

THANKS for any help !!!


This seems to be related to an issue we’re investigating where certain User-Agents are getting gzipped responses back unexpectedly.

You can likely resolve this for yourself in the meantime by explicitly setting a User-agent HTTP header that is unique to your application.