Hi Nicholas,
Sounds like you have this particular method cracked (account/
updateprofileimage) in Oauth
Our code does use C# for all twitter layers... And thanks for your
offer.. all I'm really after is the logic to get the correctly signed
POST for this method... You seem to suggest I don't
Thanks Thomas... I did look at TwitterVB as a possible way to find the
answer to this particular function call... but the API says it doesn't
yet cover account/updateprofileimage...
Thanks
Simon
On Oct 19, 3:39 pm, Thomas Hübner wrote:
> You can use TwitterVB which covers nearly the complete A
You can use TwitterVB which covers nearly the complete API in .NET
(OAuth included). U find it on codeplex http://twittervb.codeplex.com/
Cheers,
Thomas
Nicholas Granado schrieb:
> Simon,
>
> You would sign the request with all of the usual "oauth param"
> suspects. If I recall correctly this e
Simon,
You would sign the request with all of the usual "oauth param" suspects. If
I recall correctly this endpoint has no other params other than the 'image'
param in the multi-part post body whose value would be the bytes of the
image file. Typically I've only seen the post params passed into
Nicholas,
That's great feedback!
In you opinion, how do I then sign the request? Do I use all the usual
for the signaturebase... ie postmethod&url&nonce&etc etc
or just postmethod&url& as David suggested?
I trust that the image data does not come into the signing process,
and that I still can po
Simon,
I believe the body of your post might be incorrect. It should look like
this:
POST /account/update_profile_image.xml HTTP/1.1
Content-Type: multipart/form-data;
boundary=8cbed79c91b24f3
Host: twitter.com
Content-Length: 3863(this will probably change now..)
---
Hi David,
I found your excellent post hoping that it would solve the same
challenge for my app: updating profile image via Oauth... using
similar .net base to yourself...
BUT I just get the 401 all the time... despite taking your advice to
just sign with the HTTPmethod & URL My post data is l
On Thu, Aug 20, 2009 at 1:40 AM, David Carson wrote:
>
> Got this sorted out and working, and thought I should share the two
> pitfalls which were causing me problems.
>
> First of all, unbelievably, the 500 Internal Server Error was being
> caused by an extra carriage return between my last HTTP
Got this sorted out and working, and thought I should share the two
pitfalls which were causing me problems.
First of all, unbelievably, the 500 Internal Server Error was being
caused by an extra carriage return between my last HTTP header and the
first multipart boundary. Seriously. I had two bl
