Thanks, I have sent you a Charles bebug output.
Interesting to see is that with a request I first get a 401
unauthorised error.
Strictly speaking, per the HTTP spec, clients should not reply with
authentication information to a resource that has not first requested it.
The 401 is to make that
What Cameron said. The first 401 is our servers saying, you need to
identify yourself. Once that happens, the request seems to go
through.
On Tue, Apr 14, 2009 at 08:36, Cameron Kaiser spec...@floodgap.com wrote:
Thanks, I have sent you a Charles bebug output.
Interesting to see is that with
I have same problem, any news yet?
On 2 apr, 19:38, Alex Payne a...@twitter.com wrote:
It is most likely a Twitter bug. We've been oscillating between two
image uploading libraries, trying to deal with issues in each.
On Wed, Apr 1, 2009 at 22:50, pianoben piano...@gmail.com wrote:
I've
On Apr 2, 10:50 am, pianoben piano...@gmail.com wrote:
I've Googled around a bit, and haven't found anything that talks about
this issue, so I humbly submit my problem to the Twitter wizards.
Here's the problem - when I call the API function
update_profile_image, the upload succeeds, and
