Hi Hayes,
I have yet to test the file upload methods via OAuth but I don't
see a reason they should not work, as Blaine stated. Let's keep the
pertinent information in the ticket so we can re-construct the issue
and the fix all in one, easy to search, place. I'll put my questions
over there and we can work through the issue.
Thanks;
— Matt Sanford / @mzsanford
On Apr 7, 2009, at 09:21 AM, Hayes Davis wrote:
I wanted to resurrect this because I didn't see an official response
in the thread. I do see a response (as of yesterday) on the related
support issue[1] but I wanted to verify a couple things.
According to this response on the OAuth GetSatisfaction[2] page,
Blaine says that multipart forms don't require that form parameters
be included in the OAuth signature. However, when I try to post to
either account/update_profile_image or account/
update_profile_background_image using OAuth without including the
params in the signature, I get back a not authenticated status. Is
it planned for this to work in the future *or* should this work now
and I'm just doing something wrong? If it should work, then I'll
happily send along my headers, etc.
[1] http://code.google.com/p/twitter-api/issues/detail?id=368
[2]
http://getsatisfaction.com/oauth/topics/can_oauth_be_used_for_file_upload#reply_563569
Thanks.
Hayes
--
Hayes Davis
@hayesdavis
On Thu, Mar 19, 2009 at 3:11 PM, Luke l...@codegent.com wrote:
I have exactly the same problem. How can we update images with OAuth?
Agree that base64 encoded would be a good workaround for now.
- Luke
@luke_bkk
On Mar 18, 8:55 pm, Zachary West zacw...@gmail.com wrote:
Hi,
It seems OAuth doesn't support multipart/form-data, at least this
version of
the OAuth spec doesn't support it. Would it be possible to also
accept a
base64-encoded, hashed (regular) argument for the image in the
POST data
instead of just the form-data submission/version?
This would make it significantly easier to submit the data, if at
all.
Zachary West
@zacwest
