[twitter-dev] Re: Why have I recieved a HTTP 601 Response.

2010-05-13 Thread Asura

yes, my proxy located in south korea.
and every sigle try to authoization are disconnected.


On May 10, 2:13 am, Raffi Krikorian ra...@twitter.com wrote:
 i'm not sure - how long do you see the connection hang before the disconnect
 occurs?  how frequently do you see this issue?  where is your proxy
 geographically located?





 On Mon, May 10, 2010 at 4:34 AM, Asura hyuckmin.k...@gmail.com wrote:
  hi,

  Actually, I'm connecting through a proxy.
  But, they saied that we just send HTTP 601 message cause twitter
  disconnects.

  when do you disconnect with client while authorize?

  your kind comment would be much appreciated.

  Thanks.
  Regards,
  H.

  On May 7, 2:42 pm, Raffi Krikorian ra...@twitter.com wrote:
   hi!

   are you connecting through a proxy or some other intermediary?  that
  failure
   doesn't seem like it came from the twitter stack.

   On Fri, May 7, 2010 at 10:10 AM, Asura hyuckmin.k...@gmail.com wrote:
I have some Twitter login problem with my Polaris 6.2 Mobile Browser
on handset device.
I’ve been trying to figure it out. But I haven’t found out a problem,
I really need you guys's answer for that.
Currently, I use the IE user agent string for compatibility.
I’ve attached some transaction log.
Please let me know, if you guys need more information.
I’m looking forward to your hopeful response.
Thank you.

  ---­­--
POSThttp://twitter.com/oauth/authorizeHTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/x-shockwave-flash, application/vnd.ms-excel, application/
vnd.ms-powerpoint, application/msword, */*
Accept-Language: ko
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0);
800*480;POLARIS 6.100;em1.0;01057407732
Host: twitter.com
Connection: Keep-Alive
Referer:
   http://twitter.com/oauth/authorize?oauth_token=QQCGC4jstIj1LN73LZxuh2.
  ..
Proxy-Authorization: Basic OTcyMjQ5NjEwNTp2enc=
Cookie: guest_id=127181804004115551;

  original_referer=LQtHfb3aVLhzTQteZqBtMsK1SG1k6PabMrGGFzkb8SWvN4rcMar6PByaoA­­j77FrM0MzwLyUG00BPri2ivfClbpZqqFy5G5VDpU5n;
auth_token=;

  _twitter_sess=BAh7CzoPY3JlYXRlZF9hdGwrCKpp52FRh4oAToOcmV0dXJuX3RvIl5odHRwOi­­8vv50AdHdpdHRlci5jb20vb2F1dGgvYXV0aG9yaXplP29hdXRoX3Rva2VuPVFRQ0dDD50ANGpz­d­ElqMUxONzNMWnh1aDJKaEtFYWVvaWZGN1hmTVNIalpSWToRdHJhbnNff50AcHJvbXB0MDoMY3­Ny­Zl9pZCIlYmRiMzYzNWJjZWQ0MjYyZjc4ZDZmODViZTUyy50ANjhiZGM6B2lkIiUxYjg2NmE0­OTl­iNjI0NDljNWUwMTc5Yjg1MWU1YmU1YiIKK50AZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcj­o6Rm­xhc2g6OkZsYXNoSGFzaHsAA50ABjoKQHVzZWR7AAA53DD53D--
c2404da8c9fd8ee2a8738deeb9f7b77d49ee0c7d;
__utmz=43838368.1271818261.2.2.utmcsr=browser.lgtelecom.com|
utmccn=(referral)|utmcmd=referral|utmcct=/svc_twitter/fb/width/prg/
information_1.htm;
__utma=43838368.114323.1271818047.1271818047.1271818261.2;
__utmc=43838368; __utmv=43838368.langgAA0en;
__utmb=43838368.4.10.1271818261
Content-Type: application/x-www-form-urlencoded
Content-Length: 186

  authenticity_token=8e936e0758e27e3bfd5dfba85e62ee418d045f6foauth_token=QQC­­GC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRYsessionnBusername_or_emaillD=minbg­7­17sessionnBpassworddD=m20062445

  ---­­--­-­
HTTP/1.1 601 Connect Fail
Connection: close
Content-Length: 55
HTMLBODYConnecting to WEB Server Fail/BODY/HTML

   --
   Raffi Krikorian
   Twitter Platform Teamhttp://twitter.com/raffi-Hide quoted text -

   - Show quoted text -

 --
 Raffi Krikorian
 Twitter Platform Teamhttp://twitter.com/raffi- Hide quoted text -

 - Show quoted text -


[twitter-dev] Re: Why have I recieved a HTTP 601 Response.

2010-05-09 Thread Asura
hi,

Actually, I'm connecting through a proxy.
But, they saied that we just send HTTP 601 message cause twitter
disconnects.

when do you disconnect with client while authorize?

your kind comment would be much appreciated.

Thanks.
Regards,
H.



On May 7, 2:42 pm, Raffi Krikorian ra...@twitter.com wrote:
 hi!

 are you connecting through a proxy or some other intermediary?  that failure
 doesn't seem like it came from the twitter stack.





 On Fri, May 7, 2010 at 10:10 AM, Asura hyuckmin.k...@gmail.com wrote:
  I have some Twitter login problem with my Polaris 6.2 Mobile Browser
  on handset device.
  I’ve been trying to figure it out. But I haven’t found out a problem,
  I really need you guys's answer for that.
  Currently, I use the IE user agent string for compatibility.
  I’ve attached some transaction log.
  Please let me know, if you guys need more information.
  I’m looking forward to your hopeful response.
  Thank you.

  ---­--
  POSThttp://twitter.com/oauth/authorizeHTTP/1.1
  Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
  application/x-shockwave-flash, application/vnd.ms-excel, application/
  vnd.ms-powerpoint, application/msword, */*
  Accept-Language: ko
  Accept-Encoding: gzip, deflate
  User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0);
  800*480;POLARIS 6.100;em1.0;01057407732
  Host: twitter.com
  Connection: Keep-Alive
  Referer:
 http://twitter.com/oauth/authorize?oauth_token=QQCGC4jstIj1LN73LZxuh2...
  Proxy-Authorization: Basic OTcyMjQ5NjEwNTp2enc=
  Cookie: guest_id=127181804004115551;

  original_referer=LQtHfb3aVLhzTQteZqBtMsK1SG1k6PabMrGGFzkb8SWvN4rcMar6PByaoA­j77FrM0MzwLyUG00BPri2ivfClbpZqqFy5G5VDpU5n;
  auth_token=;

  _twitter_sess=BAh7CzoPY3JlYXRlZF9hdGwrCKpp52FRh4oAToOcmV0dXJuX3RvIl5odHRwOi­8vv50AdHdpdHRlci5jb20vb2F1dGgvYXV0aG9yaXplP29hdXRoX3Rva2VuPVFRQ0dDD50ANGpzd­ElqMUxONzNMWnh1aDJKaEtFYWVvaWZGN1hmTVNIalpSWToRdHJhbnNff50AcHJvbXB0MDoMY3Ny­Zl9pZCIlYmRiMzYzNWJjZWQ0MjYyZjc4ZDZmODViZTUyy50ANjhiZGM6B2lkIiUxYjg2NmE0OTl­iNjI0NDljNWUwMTc5Yjg1MWU1YmU1YiIKK50AZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rm­xhc2g6OkZsYXNoSGFzaHsAA50ABjoKQHVzZWR7AAA53DD53D--
  c2404da8c9fd8ee2a8738deeb9f7b77d49ee0c7d;
  __utmz=43838368.1271818261.2.2.utmcsr=browser.lgtelecom.com|
  utmccn=(referral)|utmcmd=referral|utmcct=/svc_twitter/fb/width/prg/
  information_1.htm;
  __utma=43838368.114323.1271818047.1271818047.1271818261.2;
  __utmc=43838368; __utmv=43838368.langgAA0en;
  __utmb=43838368.4.10.1271818261
  Content-Type: application/x-www-form-urlencoded
  Content-Length: 186

  authenticity_token=8e936e0758e27e3bfd5dfba85e62ee418d045f6foauth_token=QQC­GC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRYsessionnBusername_or_emaillD=minbg7­17sessionnBpassworddD=m20062445

  ---­---­
  HTTP/1.1 601 Connect Fail
  Connection: close
  Content-Length: 55
  HTMLBODYConnecting to WEB Server Fail/BODY/HTML

 --
 Raffi Krikorian
 Twitter Platform Teamhttp://twitter.com/raffi- Hide quoted text -

 - Show quoted text -