[twitter-dev] Why have I recieved a HTTP 601 Response.
1,661 views
Skip to first unread message
Asura
May 7, 2010, 1:10:58 PM5/7/10
to Twitter Development Talk
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.
-------------------------------------------------------------------------------------------------------------------------------------------------
POST http://twitter.com/oauth/authorize HTTP/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=QQCGC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY
Proxy-Authorization: Basic OTcyMjQ5NjEwNTp2enc=
Cookie: guest_id=127181804004115551;
original_referer=LQtHfb3aVLhzTQteZqBtMsK1SG1k6PabMrGGFzkb8SWvN4rcMar6PByaoAj77FrM0MzwLyUG00BPri2ivfClbpZqqFy5G5VDpU5n;
auth_token=;
_twitter_sess=BAh7CzoPY3JlYXRlZF9hdGwrCKpp52FRh4oAToOcmV0dXJuX3RvIl5odHRwOi8vv50AdHdpdHRlci5jb20vb2F1dGgvYXV0aG9yaXplP29hdXRoX3Rva2VuPVFRQ0dDD50ANGpzdElqMUxONzNMWnh1aDJKaEtFYWVvaWZGN1hmTVNIalpSWToRdHJhbnNff50AcHJvbXB0MDoMY3NyZl9pZCIlYmRiMzYzNWJjZWQ0MjYyZjc4ZDZmODViZTUyy50ANjhiZGM6B2lkIiUxYjg2NmE0OTliNjI0NDljNWUwMTc5Yjg1MWU1YmU1YiIKK50AZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsAA50ABjoKQHVzZWR7AAA53DD53D--
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.1143231111.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=8e936e0758e27e3bfd5dfba85e62ee418d045f6f&oauth_token=QQCGC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY&sessionnBusername_or_emaillD=minbg717&sessionnBpassworddD=m20062445
--------------------------------------------------------------------------------------------------------------------------------------------------------------
HTTP/1.1 601 Connect Fail
Connection: close
Content-Length: 55
<HTML><BODY>Connecting to WEB Server Fail</BODY></HTML>
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.
-------------------------------------------------------------------------------------------------------------------------------------------------
POST http://twitter.com/oauth/authorize HTTP/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=QQCGC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY
Proxy-Authorization: Basic OTcyMjQ5NjEwNTp2enc=
Cookie: guest_id=127181804004115551;
original_referer=LQtHfb3aVLhzTQteZqBtMsK1SG1k6PabMrGGFzkb8SWvN4rcMar6PByaoAj77FrM0MzwLyUG00BPri2ivfClbpZqqFy5G5VDpU5n;
auth_token=;
_twitter_sess=BAh7CzoPY3JlYXRlZF9hdGwrCKpp52FRh4oAToOcmV0dXJuX3RvIl5odHRwOi8vv50AdHdpdHRlci5jb20vb2F1dGgvYXV0aG9yaXplP29hdXRoX3Rva2VuPVFRQ0dDD50ANGpzdElqMUxONzNMWnh1aDJKaEtFYWVvaWZGN1hmTVNIalpSWToRdHJhbnNff50AcHJvbXB0MDoMY3NyZl9pZCIlYmRiMzYzNWJjZWQ0MjYyZjc4ZDZmODViZTUyy50ANjhiZGM6B2lkIiUxYjg2NmE0OTliNjI0NDljNWUwMTc5Yjg1MWU1YmU1YiIKK50AZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsAA50ABjoKQHVzZWR7AAA53DD53D--
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.1143231111.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=8e936e0758e27e3bfd5dfba85e62ee418d045f6f&oauth_token=QQCGC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY&sessionnBusername_or_emaillD=minbg717&sessionnBpassworddD=m20062445
--------------------------------------------------------------------------------------------------------------------------------------------------------------
HTTP/1.1 601 Connect Fail
Connection: close
Content-Length: 55
<HTML><BODY>Connecting to WEB Server Fail</BODY></HTML>
Raffi Krikorian
May 7, 2010, 5:42:30 PM5/7/10
to twitter-deve...@googlegroups.com
hi!
are you connecting through a proxy or some other intermediary? that failure doesn't seem like it came from the twitter stack.
Asura
May 9, 2010, 11:34:13 PM5/9/10
to Twitter Development Talk
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
> > auth_token=;
>
> > _twitter_sess=BAh7CzoPY3JlYXRlZF9hdGwrCKpp52FRh4oAToOcmV0dXJuX3RvIl5odHRwOi8vv50AdHdpdHRlci5jb20vb2F1dGgvYXV0aG9yaXplP29hdXRoX3Rva2VuPVFRQ0dDD50ANGpzdElqMUxONzNMWnh1aDJKaEtFYWVvaWZGN1hmTVNIalpSWToRdHJhbnNff50AcHJvbXB0MDoMY3NyZl9pZCIlYmRiMzYzNWJjZWQ0MjYyZjc4ZDZmODViZTUyy50ANjhiZGM6B2lkIiUxYjg2NmE0OTliNjI0NDljNWUwMTc5Yjg1MWU1YmU1YiIKK50AZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsAA50ABjoKQHVzZWR7AAA53DD53D--
>
> > --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> - Show quoted text -
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...
> > 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:
> > Proxy-Authorization: Basic OTcyMjQ5NjEwNTp2enc=
> > Cookie: guest_id=127181804004115551;
>
> > original_referer=LQtHfb3aVLhzTQteZqBtMsK1SG1k6PabMrGGFzkb8SWvN4rcMar6PByaoAj77FrM0MzwLyUG00BPri2ivfClbpZqqFy5G5VDpU5n;
> > Cookie: guest_id=127181804004115551;
>
> > auth_token=;
>
> > _twitter_sess=BAh7CzoPY3JlYXRlZF9hdGwrCKpp52FRh4oAToOcmV0dXJuX3RvIl5odHRwOi8vv50AdHdpdHRlci5jb20vb2F1dGgvYXV0aG9yaXplP29hdXRoX3Rva2VuPVFRQ0dDD50ANGpzdElqMUxONzNMWnh1aDJKaEtFYWVvaWZGN1hmTVNIalpSWToRdHJhbnNff50AcHJvbXB0MDoMY3NyZl9pZCIlYmRiMzYzNWJjZWQ0MjYyZjc4ZDZmODViZTUyy50ANjhiZGM6B2lkIiUxYjg2NmE0OTliNjI0NDljNWUwMTc5Yjg1MWU1YmU1YiIKK50AZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsAA50ABjoKQHVzZWR7AAA53DD53D--
> > 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.1143231111.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=8e936e0758e27e3bfd5dfba85e62ee418d045f6f&oauth_token=QQCGC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY&sessionnBusername_or_emaillD=minbg717&sessionnBpassworddD=m20062445
> > __utmz=43838368.1271818261.2.2.utmcsr=browser.lgtelecom.com|
> > utmccn=(referral)|utmcmd=referral|utmcct=/svc_twitter/fb/width/prg/
> > information_1.htm;
> > __utma=43838368.1143231111.1271818047.1271818047.1271818261.2;
> > __utmc=43838368; __utmv=43838368.langgAA0en;
> > __utmb=43838368.4.10.1271818261
> > Content-Type: application/x-www-form-urlencoded
> > Content-Length: 186
>
>
> > --------------------------------------------------------------------------------------------------------------------------------------------------------------
> > HTTP/1.1 601 Connect Fail
> > Connection: close
> > Content-Length: 55
> > <HTML><BODY>Connecting to WEB Server Fail</BODY></HTML>
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi- Hide quoted text -
> > Connection: close
> > Content-Length: 55
> > <HTML><BODY>Connecting to WEB Server Fail</BODY></HTML>
>
> --
> Raffi Krikorian
>
> - Show quoted text -
Raffi Krikorian
May 10, 2010, 5:13:33 AM5/10/10
to twitter-deve...@googlegroups.com
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?
Asura
May 13, 2010, 5:58:41 PM5/13/10
to Twitter Development Talk
yes, my proxy located in south korea.
and every sigle try to authoization are disconnected.
> > > > 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.1143231111.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=8e936e0758e27e3bfd5dfba85e62ee418d045f6f&oauth_token=QQCGC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY&sessionnBusername_or_emaillD=minbg717&sessionnBpassworddD=m20062445
> > > > __utmz=43838368.1271818261.2.2.utmcsr=browser.lgtelecom.com|
> > > > utmccn=(referral)|utmcmd=referral|utmcct=/svc_twitter/fb/width/prg/
> > > > information_1.htm;
> > > > __utma=43838368.1143231111.1271818047.1271818047.1271818261.2;
> > > > __utmc=43838368; __utmv=43838368.langgAA0en;
> > > > __utmb=43838368.4.10.1271818261
> > > > Content-Type: application/x-www-form-urlencoded
> > > > Content-Length: 186
>
>
> > --------------------------------------------------------------------------------------------------------------------------------------------------------------
> > > > HTTP/1.1 601 Connect Fail
> > > > Connection: close
> > > > Content-Length: 55
> > > > <HTML><BODY>Connecting to WEB Server Fail</BODY></HTML>
>
> > > --
> > > Raffi Krikorian
> > > Twitter Platform Teamhttp://twitter.com/raffi-Hide quoted text -
> > > > Connection: close
> > > > Content-Length: 55
> > > > <HTML><BODY>Connecting to WEB Server Fail</BODY></HTML>
>
> > > --
> > > Raffi Krikorian
Reply all
Reply to author
Forward
0 new messages