It seems like a number of different HTTP client libraries have issues with this method. However, it works just fine via curl, which leads me to believe that the problem is either with those libraries with the programmer's use of the libraries.
On Sun, Jan 4, 2009 at 06:41, avon <[email protected]> wrote: > > Has this been solved? Im getting the same error when I try to upload > an image > > On Dec 17 2008, 1:48 am, Toby Glenn <[email protected]> wrote: >> I get the 500 Internal Server Error when I try to update a profile >> image. I am trying to do it using c# and I am not sure what is going >> on. Here is a network sniff of my request: >> No. Time Source Destination >> Protocol Info >> 657 2.775514 10.50.50.230 128.121.146.100 >> HTTP POST /account/update_profile_image.xml HTTP/1.1 (JPEG JFIF >> image) >> >> Frame 657 (85 bytes on wire, 85 bytes captured) >> Ethernet II, Src: 00:21:70:6b:00:61 (00:21:70:6b:00:61), Dst: >> Watchgua_30:99:52 (00:90:7f:30:99:52) >> Destination: Watchgua_30:99:52 (00:90:7f:30:99:52) >> Source: 00:21:70:6b:00:61 (00:21:70:6b:00:61) >> Type: IP (0x0800) >> Internet Protocol, Src: 10.50.50.230 (10.50.50.230), Dst: >> 128.121.146.100 (128.121.146.100) >> Transmission Control Protocol, Src Port: hfcs (4900), Dst Port: http >> (80), Seq: 28021, Ack: 26, Len: 31 >> [Reassembled TCP Segments (28051 bytes): #586(210), #621(129), #622 >> (1260), #623(1260), #627(1260), #628(1260), #629(1260), #630(1260), >> #632(1260), #633(1260), #634(1260), #635(1260), #636(1260), #638 >> (1260), #639(1260), #640(1260), #641(1260] >> Hypertext Transfer Protocol >> MIME Multipart Media Encapsulation, Type: multipart/form-data, >> Boundary: "----------8cb2dd5e785fac4" >> [Type: multipart/form-data] >> First boundary: ------------8cb2dd5e785fac4\r\n >> Encapsulated multipart part: (image/jpeg) >> Boundary: \r\n------------8cb2dd5e785fac4\r\n >> Encapsulated multipart part: > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
