Also worth noting: there was no error returned - it hung up after 3/4 seconds. If you connect to twitter.com port 80 using hyperterminal / winsock, you can copy and paste (replacing the authorisation, and enabling append line feeds onto line ends in hyperterminal options) my examples and see this for yourself.
Any other ideas? I would really appreciate any comments on this issue. On Mar 19, 3:16 pm, Oli <oliverst...@gmail.com> wrote: > Hi there, > > I've just been playing about and have come across a curious bug (I > have changed one letter of the hashcode) - connecting and sending > > POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 > Host: twitter.com > Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== > Content-type: application/x-www-form-urlencoded > Content-length: 36 > Connection: Close > > status=ALAhM%3A+Test_Unit+t1%3A35tej > > DOESN'T WORK but > > POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 > Host: twitter.com > Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== > Content-type: application/x-www-form-urlencoded > Content-length: 35 > Connection: Close > > status=ALAhM%3A+Test_Unit+t1%3A35te > > DOES - why is this?? Many thanks in advance To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
