Was the cause of the empty response body ever discovered? I'm having
a similar issue, except my 401 response body has Content-Length: 1
containing an empty space .
On Nov 19 2010, 3:44 pm, Matt Harris thematthar...@twitter.com
wrote:
Hey Chrys,
Agreed. The authentication header doesn't have
Hey Chrys,
The order of the parameters in the base string matter and they should be in
lexicollexicographical order. For ease of debugging and to remove any
ambiguity it would be better to have the authorization header use the same
order too.
Can you tell me what the body content of the 401
Twitter 401 error is related to Authentication
401 Unauthorized: Authentication credentials were missing or
incorrect.
Another debugging is to print out error type error message from iPhone
console
On Nov 19, 11:04 am, Matt Harris thematthar...@twitter.com wrote:
Hey Chrys,
The order of the
Hey Matt,
I am using Loren Brichter's OAuthCore library to create the
Authorization header... so I imagine he did it correctly.
The body content of the 401 is empty. Content-Length: 0
On Nov 19, 11:04 am, Matt Harris thematthar...@twitter.com wrote:
Hey Chrys,
The order of the parameters in
Yeah, I've done that. Authentication credentials meaning my oAuth
credentials, or xAuth credentials?
On Nov 19, 11:41 am, Bess bess...@gmail.com wrote:
Twitter 401 error is related to Authentication
401 Unauthorized: Authentication credentials were missing or
incorrect.
Another debugging is
Also, the example here shows that the Auth header and the base string
aren't in the same order:
http://dev.twitter.com/pages/xauth
On Nov 19, 11:04 am, Matt Harris thematthar...@twitter.com wrote:
Hey Chrys,
The order of the parameters in the base string matter and they should be in
Hey Chrys,
Agreed. The authentication header doesn't have to be in order but as said
previously, it helps with debugging.
It is really strange that the response body is empty. It maybe easier if you
email me the full request headers, with response headers and content so I
can debug further. For
*bump*
I've run my base string through an oAuth verifier (http://quonos.nl/
oauthTester/), and it all checks out!
Any ideas?
On Oct 27, 4:50 pm, Chrys Bader chr...@gmail.com wrote:
Hey all,
This is my first post in this group, hi!
I am having trouble making a request
Hey Chrys,
A couple of things to check first:
1. Have you been granted xAuth access?
2. Double check the timestamp of your request is within 10 or so
minutes of the time returned by Twitter's servers. Our server time is
in UTC.
3. Verify your encoding is correct. For example: a password like ab$
1. Yes
2. Interesting point. I'm probably not sending a UTC timestamp!
3. We take care of this
Thanks! I'm going to play with the timstamp.
On Nov 18, 5:53 pm, themattharris thematthar...@twitter.com wrote:
Hey Chrys,
A couple of things to check first:
1. Have you been granted xAuth access?
Ok, I looked into it. According to the iPhone SDK documentation, I am
indeed sending the UTC (GMT) timestamp.
Still not sure what else could be wrong?
Is this the right Content-Type?
Content-Type = application/x-www-form-urlencoded; charset=utf-8;
On Nov 18, 5:53 pm, themattharris
OK, but is the UTC timestamp actually accurate? we've heard of a number of
phones whose date/time are wildly wrong. It maybe find but it's quite
common.
Your content-type is fine.
Matt
On Thu, Nov 18, 2010 at 6:03 PM, Chrys Bader chr...@gmail.com wrote:
Ok, I looked into it. According to the
Yes I compared the UTC timestamp that my phone is generating with the
actual UTC timestamp, and they were the same.
Is there anything else I can show you for more information?
No matter what, I just keep getting a 401 response from Twitter.
On Nov 18, 6:41 pm, Matt Harris
Does the order of the params in either the Authorization or Base
string matter?
Here are my Request Headers:
Authorization = OAuth oauth_timestamp=\1290134876\, oauth_nonce=
\D3EC42D2-A37F-4298-987D-0F9603B0C9C7\, oauth_version=\1.0\,
oauth_consumer_key=\xxx\,
14 matches
Mail list logo
