Re: [twitter-dev] Re: The remote server returned an error: (401) Unauthorized
Twitter doesn't really care about IPs - unless you are doing things really, really, really wrong. Assuming that the signature generation stays the same (some platforms have little-endian BO, big-endian BO, etc, and that may change the algorithm a bit, but when windows-windows that doesn't really apply), the most likely cause of this error is the timestamp of the computer running the application. Tom On 8/10/10 12:07 PM, punit khaire wrote: Hey Taylor Thanks,for reply, My problem redirect is solved.Now the problem is , I developed website for twitter OAuth using .net 2.0,I deployed that application in public IP, and suddenly I got following error, /An existing connection was forcibly closed by the remote host./ But when I run the same application from localhost on same IP,It is working fine.And gives error when It redirected to my Public IP Call back URl. I couldnt figure out is it website issue or Public IP issue. Thanks for help in advance, Punit On Mon, Aug 9, 2010 at 7:45 PM, Taylor Singletary taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com wrote: Hi Punit, First, some advice: I recommend using HTTP header-based OAuth rather than putting your OAuth parameters directly in the query string. It separates concerns and makes your debugging ultimately easier. That said, the first issue you're probably running into is that you aren't URL-encoding your OAuth Callback properly. In fact, when you're presenting any of these OAuth parameters, whether it was via HTTP header or query string, you need to do some more escaping. For our servers to properly interpret the URL you are sending, your request would need to look a bit more like (noting that the signature would be significantly different as a result): http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 Are you using an OAuth library for this? Taylor On Sat, Aug 7, 2010 at 5:32 PM, execut...@gmail.com execut...@gmail.com mailto:execut...@gmail.com wrote: the link below is broken,, On Sat, Aug 7, 2010 at 4:44 PM, Tom allerleiga...@gmail.com mailto:allerleiga...@gmail.com wrote: How are you generating the signature? Tom On Aug 7, 2:43 pm, Punit.khaire punit.kha...@gmail.com mailto:punit.kha...@gmail.com wrote: Hi guys, I started to work on the twitter application .Our main task is to tweet messages using oAuth authentication. I am sending below request using GET method, http://api.twitter.com/oauth/request_token?oauth_callback=http://203 When I manually hit the above URl I get following error message, Failed to validate oauth signature and token I dont understand y I get this message,as I am sending everything in my parameter list. Am I missing something here,thanks in advance for any help. -- -- Michael J.D Saguri 1-250-999-0890 http://www.tweep.net http://www.tweep.net/ Skype: marketingmaniac
Re: [twitter-dev] Re: The remote server returned an error: (401) Unauthorized
Hi, Thanks, for the reply, But then why site working from the localhost on the same Computer.But If I accessed it from Public IP it returns error. Thanks, Punit Khaire. On Tue, Aug 10, 2010 at 4:13 PM, Tom van der Woerdt i...@tvdw.eu wrote: Twitter doesn't really care about IPs - unless you are doing things really, really, really wrong. Assuming that the signature generation stays the same (some platforms have little-endian BO, big-endian BO, etc, and that may change the algorithm a bit, but when windows-windows that doesn't really apply), the most likely cause of this error is the timestamp of the computer running the application. Tom On 8/10/10 12:07 PM, punit khaire wrote: Hey Taylor Thanks,for reply, My problem redirect is solved.Now the problem is , I developed website for twitter OAuth using .net 2.0,I deployed that application in public IP, and suddenly I got following error, /An existing connection was forcibly closed by the remote host./ But when I run the same application from localhost on same IP,It is working fine.And gives error when It redirected to my Public IP Call back URl. I couldnt figure out is it website issue or Public IP issue. Thanks for help in advance, Punit On Mon, Aug 9, 2010 at 7:45 PM, Taylor Singletary taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com wrote: Hi Punit, First, some advice: I recommend using HTTP header-based OAuth rather than putting your OAuth parameters directly in the query string. It separates concerns and makes your debugging ultimately easier. That said, the first issue you're probably running into is that you aren't URL-encoding your OAuth Callback properly. In fact, when you're presenting any of these OAuth parameters, whether it was via HTTP header or query string, you need to do some more escaping. For our servers to properly interpret the URL you are sending, your request would need to look a bit more like (noting that the signature would be significantly different as a result): http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 Are you using an OAuth library for this? Taylor On Sat, Aug 7, 2010 at 5:32 PM, execut...@gmail.com execut...@gmail.com mailto:execut...@gmail.com wrote: the link below is broken,, On Sat, Aug 7, 2010 at 4:44 PM, Tom allerleiga...@gmail.com mailto:allerleiga...@gmail.com wrote: How are you generating the signature? Tom On Aug 7, 2:43 pm, Punit.khaire punit.kha...@gmail.com mailto:punit.kha...@gmail.com wrote: Hi guys, I started to work on the twitter application .Our main task is to tweet messages using oAuth authentication. I am sending below request using GET method, http://api.twitter.com/oauth/request_token?oauth_callback=http://203 When I manually hit the above URl I get following error message, Failed to validate oauth signature and token I dont understand y I get this message,as I am sending everything in my parameter list. Am I missing something here,thanks in advance for any help. -- -- Michael J.D Saguri 1-250-999-0890 http://www.tweep.net http://www.tweep.net/ Skype: marketingmaniac
Re: [twitter-dev] Re: The remote server returned an error: (401) Unauthorized
Oh, it's the same computer? In that case, my timestamp issue doesn't apply. You should check that all localhost URLs have been removed and changed to the public addresses. That's all I can think of - like I already said, OAuth (and Twitter) doesn't really care about IP addresses. Tom On 8/10/10 1:11 PM, punit khaire wrote: Hi, Thanks, for the reply, But then why site working from the localhost on the same Computer.But If I accessed it from Public IP it returns error. Thanks, Punit Khaire. On Tue, Aug 10, 2010 at 4:13 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: Twitter doesn't really care about IPs - unless you are doing things really, really, really wrong. Assuming that the signature generation stays the same (some platforms have little-endian BO, big-endian BO, etc, and that may change the algorithm a bit, but when windows-windows that doesn't really apply), the most likely cause of this error is the timestamp of the computer running the application. Tom On 8/10/10 12:07 PM, punit khaire wrote: Hey Taylor Thanks,for reply, My problem redirect is solved.Now the problem is , I developed website for twitter OAuth using .net 2.0,I deployed that application in public IP, and suddenly I got following error, /An existing connection was forcibly closed by the remote host./ But when I run the same application from localhost on same IP,It is working fine.And gives error when It redirected to my Public IP Call back URl. I couldnt figure out is it website issue or Public IP issue. Thanks for help in advance, Punit On Mon, Aug 9, 2010 at 7:45 PM, Taylor Singletary taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com wrote: Hi Punit, First, some advice: I recommend using HTTP header-based OAuth rather than putting your OAuth parameters directly in the query string. It separates concerns and makes your debugging ultimately easier. That said, the first issue you're probably running into is that you aren't URL-encoding your OAuth Callback properly. In fact, when you're presenting any of these OAuth parameters, whether it was via HTTP header or query string, you need to do some more escaping. For our servers to properly interpret the URL you are sending, your request would need to look a bit more like (noting that the signature would be significantly different as a result): http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 Are you using an OAuth library for this? Taylor On Sat, Aug 7, 2010 at 5:32 PM, execut...@gmail.com execut...@gmail.com mailto:execut...@gmail.com mailto:execut...@gmail.com mailto:execut...@gmail.com wrote: the link below is broken,, On Sat, Aug 7, 2010 at 4:44 PM, Tom allerleiga...@gmail.com mailto:allerleiga...@gmail.com mailto:allerleiga...@gmail.com mailto:allerleiga...@gmail.com wrote: How are you generating the signature? Tom On Aug 7, 2:43 pm, Punit.khaire punit.kha...@gmail.com mailto:punit.kha...@gmail.com mailto:punit.kha...@gmail.com mailto:punit.kha...@gmail.com wrote:
Re: [twitter-dev] Re: The remote server returned an error: (401) Unauthorized
Sorry for the double post, but I just realized: is your public IP firewalled? That could possibly be the issue. Also, is the error you are getting a Firefox (or any browser) error, or an OAuth/Twitter error? Tom On 8/10/10 1:11 PM, punit khaire wrote: Hi, Thanks, for the reply, But then why site working from the localhost on the same Computer.But If I accessed it from Public IP it returns error. Thanks, Punit Khaire. On Tue, Aug 10, 2010 at 4:13 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: Twitter doesn't really care about IPs - unless you are doing things really, really, really wrong. Assuming that the signature generation stays the same (some platforms have little-endian BO, big-endian BO, etc, and that may change the algorithm a bit, but when windows-windows that doesn't really apply), the most likely cause of this error is the timestamp of the computer running the application. Tom On 8/10/10 12:07 PM, punit khaire wrote: Hey Taylor Thanks,for reply, My problem redirect is solved.Now the problem is , I developed website for twitter OAuth using .net 2.0,I deployed that application in public IP, and suddenly I got following error, /An existing connection was forcibly closed by the remote host./ But when I run the same application from localhost on same IP,It is working fine.And gives error when It redirected to my Public IP Call back URl. I couldnt figure out is it website issue or Public IP issue. Thanks for help in advance, Punit On Mon, Aug 9, 2010 at 7:45 PM, Taylor Singletary taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com wrote: Hi Punit, First, some advice: I recommend using HTTP header-based OAuth rather than putting your OAuth parameters directly in the query string. It separates concerns and makes your debugging ultimately easier. That said, the first issue you're probably running into is that you aren't URL-encoding your OAuth Callback properly. In fact, when you're presenting any of these OAuth parameters, whether it was via HTTP header or query string, you need to do some more escaping. For our servers to properly interpret the URL you are sending, your request would need to look a bit more like (noting that the signature would be significantly different as a result): http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 Are you using an OAuth library for this? Taylor On Sat, Aug 7, 2010 at 5:32 PM, execut...@gmail.com execut...@gmail.com mailto:execut...@gmail.com mailto:execut...@gmail.com mailto:execut...@gmail.com wrote: the link below is broken,, On Sat, Aug 7, 2010 at 4:44 PM, Tom allerleiga...@gmail.com mailto:allerleiga...@gmail.com mailto:allerleiga...@gmail.com mailto:allerleiga...@gmail.com wrote: How are you generating the signature? Tom On Aug 7, 2:43 pm, Punit.khaire punit.kha...@gmail.com mailto:punit.kha...@gmail.com mailto:punit.kha...@gmail.com mailto:punit.kha...@gmail.com wrote: Hi guys, I started to work on the
Re: [twitter-dev] Re: The remote server returned an error: (401) Unauthorized
Thanks Tom, We are using Eset antivirus and it is also firewalled.I am getting below error when executing Request token API, *An existing connection was forcibly closed by the remote host* For more info you can hit below URL, http://203.78.217.115/TwitterOAUTH/Default.aspx Thanks, Punit. On Tue, Aug 10, 2010 at 4:45 PM, Tom van der Woerdt i...@tvdw.eu wrote: Sorry for the double post, but I just realized: is your public IP firewalled? That could possibly be the issue. Also, is the error you are getting a Firefox (or any browser) error, or an OAuth/Twitter error? Tom On 8/10/10 1:11 PM, punit khaire wrote: Hi, Thanks, for the reply, But then why site working from the localhost on the same Computer.But If I accessed it from Public IP it returns error. Thanks, Punit Khaire. On Tue, Aug 10, 2010 at 4:13 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: Twitter doesn't really care about IPs - unless you are doing things really, really, really wrong. Assuming that the signature generation stays the same (some platforms have little-endian BO, big-endian BO, etc, and that may change the algorithm a bit, but when windows-windows that doesn't really apply), the most likely cause of this error is the timestamp of the computer running the application. Tom On 8/10/10 12:07 PM, punit khaire wrote: Hey Taylor Thanks,for reply, My problem redirect is solved.Now the problem is , I developed website for twitter OAuth using .net 2.0,I deployed that application in public IP, and suddenly I got following error, /An existing connection was forcibly closed by the remote host./ But when I run the same application from localhost on same IP,It is working fine.And gives error when It redirected to my Public IP Call back URl. I couldnt figure out is it website issue or Public IP issue. Thanks for help in advance, Punit On Mon, Aug 9, 2010 at 7:45 PM, Taylor Singletary taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com wrote: Hi Punit, First, some advice: I recommend using HTTP header-based OAuth rather than putting your OAuth parameters directly in the query string. It separates concerns and makes your debugging ultimately easier. That said, the first issue you're probably running into is that you aren't URL-encoding your OAuth Callback properly. In fact, when you're presenting any of these OAuth parameters, whether it was via HTTP header or query string, you need to do some more escaping. For our servers to properly interpret the URL you are sending, your request would need to look a bit more like (noting that the signature would be significantly different as a result): http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 Are you using an OAuth library for this? Taylor On Sat, Aug 7, 2010 at 5:32 PM, execut...@gmail.com execut...@gmail.com mailto:execut...@gmail.com mailto:execut...@gmail.com mailto:execut...@gmail.com wrote: the link below is broken,, On Sat, Aug 7, 2010 at 4:44 PM, Tom allerleiga...@gmail.com mailto:allerleiga...@gmail.com
Re: [twitter-dev] Re: The remote server returned an error: (401) Unauthorized
Ah, okay, you mean the .NET error page. Well, to be honest, I don't know a bit about .NET. Luckily, I do know how Twitter works :-) Can you show a dump of the request to Twitter? (Could it be that the error you get is because Twitter generates a 401 error? In that case, your signature generation may be wrong.) Tom On 8/10/10 1:21 PM, punit khaire wrote: Thanks Tom, We are using Eset antivirus and it is also firewalled.I am getting below error when executing Request token API, /An existing connection was forcibly closed by the remote host/ For more info you can hit below URL, http://203.78.217.115/TwitterOAUTH/Default.aspx Thanks, Punit. On Tue, Aug 10, 2010 at 4:45 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: Sorry for the double post, but I just realized: is your public IP firewalled? That could possibly be the issue. Also, is the error you are getting a Firefox (or any browser) error, or an OAuth/Twitter error? Tom On 8/10/10 1:11 PM, punit khaire wrote: Hi, Thanks, for the reply, But then why site working from the localhost on the same Computer.But If I accessed it from Public IP it returns error. Thanks, Punit Khaire. On Tue, Aug 10, 2010 at 4:13 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu mailto:i...@tvdw.eu mailto:i...@tvdw.eu wrote: Twitter doesn't really care about IPs - unless you are doing things really, really, really wrong. Assuming that the signature generation stays the same (some platforms have little-endian BO, big-endian BO, etc, and that may change the algorithm a bit, but when windows-windows that doesn't really apply), the most likely cause of this error is the timestamp of the computer running the application. Tom On 8/10/10 12:07 PM, punit khaire wrote: Hey Taylor Thanks,for reply, My problem redirect is solved.Now the problem is , I developed website for twitter OAuth using .net 2.0,I deployed that application in public IP, and suddenly I got following error, /An existing connection was forcibly closed by the remote host./ But when I run the same application from localhost on same IP,It is working fine.And gives error when It redirected to my Public IP Call back URl. I couldnt figure out is it website issue or Public IP issue. Thanks for help in advance, Punit On Mon, Aug 9, 2010 at 7:45 PM, Taylor Singletary taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com wrote: Hi Punit, First, some advice: I recommend using HTTP header-based OAuth rather than putting your OAuth parameters directly in the query string. It separates concerns and makes your debugging ultimately easier. That said, the first issue you're probably running into is that you aren't URL-encoding your OAuth Callback properly. In fact, when you're presenting any of these OAuth parameters, whether it was via HTTP header or query string, you need to do some more escaping. For our servers to properly interpret the URL you are sending, your request would need to look a bit more like (noting that the signature would be significantly different as a result): http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0
Re: [twitter-dev] Re: The remote server returned an error: (401) Unauthorized
The error 401 is at initail stage now as I said below is the error I think it is not resolving the ports properly.Because it is running on port but not working on any other port. Thanks, Punit. On Tue, Aug 10, 2010 at 4:56 PM, Tom van der Woerdt i...@tvdw.eu wrote: Ah, okay, you mean the .NET error page. Well, to be honest, I don't know a bit about .NET. Luckily, I do know how Twitter works :-) Can you show a dump of the request to Twitter? (Could it be that the error you get is because Twitter generates a 401 error? In that case, your signature generation may be wrong.) Tom On 8/10/10 1:21 PM, punit khaire wrote: Thanks Tom, We are using Eset antivirus and it is also firewalled.I am getting below error when executing Request token API, /An existing connection was forcibly closed by the remote host/ For more info you can hit below URL, http://203.78.217.115/TwitterOAUTH/Default.aspx Thanks, Punit. On Tue, Aug 10, 2010 at 4:45 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: Sorry for the double post, but I just realized: is your public IP firewalled? That could possibly be the issue. Also, is the error you are getting a Firefox (or any browser) error, or an OAuth/Twitter error? Tom On 8/10/10 1:11 PM, punit khaire wrote: Hi, Thanks, for the reply, But then why site working from the localhost on the same Computer.But If I accessed it from Public IP it returns error. Thanks, Punit Khaire. On Tue, Aug 10, 2010 at 4:13 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu mailto:i...@tvdw.eu mailto:i...@tvdw.eu wrote: Twitter doesn't really care about IPs - unless you are doing things really, really, really wrong. Assuming that the signature generation stays the same (some platforms have little-endian BO, big-endian BO, etc, and that may change the algorithm a bit, but when windows-windows that doesn't really apply), the most likely cause of this error is the timestamp of the computer running the application. Tom On 8/10/10 12:07 PM, punit khaire wrote: Hey Taylor Thanks,for reply, My problem redirect is solved.Now the problem is , I developed website for twitter OAuth using .net 2.0,I deployed that application in public IP, and suddenly I got following error, /An existing connection was forcibly closed by the remote host./ But when I run the same application from localhost on same IP,It is working fine.And gives error when It redirected to my Public IP Call back URl. I couldnt figure out is it website issue or Public IP issue. Thanks for help in advance, Punit On Mon, Aug 9, 2010 at 7:45 PM, Taylor Singletary taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com wrote: Hi Punit, First, some advice: I recommend using HTTP header-based OAuth rather than putting your OAuth parameters directly in the query string. It separates concerns and makes your debugging ultimately easier. That said, the first issue you're probably running into is that you aren't URL-encoding your OAuth Callback properly. In fact, when you're presenting any of these OAuth parameters, whether it was via HTTP header or query string, you need to do some more escaping. For our servers to properly interpret the URL you are sending, your request would need to look a bit more like (noting that the signature would be significantly different as a result): http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0
Re: [twitter-dev] Re: The remote server returned an error: (401) Unauthorized
Hi Punit, First, some advice: I recommend using HTTP header-based OAuth rather than putting your OAuth parameters directly in the query string. It separates concerns and makes your debugging ultimately easier. That said, the first issue you're probably running into is that you aren't URL-encoding your OAuth Callback properly. In fact, when you're presenting any of these OAuth parameters, whether it was via HTTP header or query string, you need to do some more escaping. For our servers to properly interpret the URL you are sending, your request would need to look a bit more like (noting that the signature would be significantly different as a result): http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 Are you using an OAuth library for this? Taylor On Sat, Aug 7, 2010 at 5:32 PM, execut...@gmail.com execut...@gmail.comwrote: the link below is broken,, On Sat, Aug 7, 2010 at 4:44 PM, Tom allerleiga...@gmail.com wrote: How are you generating the signature? Tom On Aug 7, 2:43 pm, Punit.khaire punit.kha...@gmail.com wrote: Hi guys, I started to work on the twitter application .Our main task is to tweet messages using oAuth authentication. I am sending below request using GET method, http://api.twitter.com/oauth/request_token?oauth_callback=http://203.. .. When I manually hit the above URl I get following error message, Failed to validate oauth signature and token I dont understand y I get this message,as I am sending everything in my parameter list. Am I missing something here,thanks in advance for any help. -- -- Michael J.D Saguri 1-250-999-0890 http://www.tweep.net Skype: marketingmaniac
Re: [twitter-dev] Re: The remote server returned an error: (401) Unauthorized
the link below is broken,, On Sat, Aug 7, 2010 at 4:44 PM, Tom allerleiga...@gmail.com wrote: How are you generating the signature? Tom On Aug 7, 2:43 pm, Punit.khaire punit.kha...@gmail.com wrote: Hi guys, I started to work on the twitter application .Our main task is to tweet messages using oAuth authentication. I am sending below request using GET method, http://api.twitter.com/oauth/request_token?oauth_callback=http://203 When I manually hit the above URl I get following error message, Failed to validate oauth signature and token I dont understand y I get this message,as I am sending everything in my parameter list. Am I missing something here,thanks in advance for any help. -- -- Michael J.D Saguri 1-250-999-0890 http://www.tweep.net Skype: marketingmaniac
