Now that I'm clear... 1) It works for me using telnet. This may or may not be subtly different from hyperterminal. 2) Note that if you do this repeatedly with the same status text you'll get rejections due to duplicate tweets. On twitter.com this returns a 200 with no response body. You shouldn't be using this endpoint anyway, please use api.twitter.com instead.
---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 10:33 AM, Oli <oliverst...@gmail.com> wrote: > Hi Mark, thanks for your response but I think you may be mistaken. > > In the first call, I do send 36 bytes I state prior to sending - > "status=ALAhM%3A+Test_Unit+t1%3A35tej" > In the second call, I do send the 35 bytes I state prior to sending - > "status=ALAhM%3A+Test_Unit+t1%3A35te" > > Additionally, I am 100% sure there are no spaces at the end / other > chars that are hidden. > > I am dealing with the raw socket and to rule out any software mishap I > have been testing manually using hyperterminal (winsock) to diagnose > the problem. > > I'm at a dead end on this until somebody can figure out what I am > doing wrong / if there is genuinely a problem elsewhere. Thanks again > > > On Mar 19, 4:58 pm, Mark McBride <mmcbr...@twitter.com> wrote: > > On to the real problem, are you using a library to make that POST > request, > > or raw sockets? What is likely happening is you're telling the server to > > expect 36 bytes of info in the first call. You send 35. The server > waits > > and waits then hangs up. In the second call you're telling the server to > > expect 35, you send 35, the server does it's deal, and everybody is > happy. > > > > ---Mark > > > > http://twitter.com/mccv > > > > On Fri, Mar 19, 2010 at 9:55 AM, Mark McBride <mmcbr...@twitter.com> > wrote: > > > Missed the part about the one letter change. Clever! > > > > > ---Mark > > > > >http://twitter.com/mccv > > > > > On Fri, Mar 19, 2010 at 9:54 AM, Mark McBride <mmcbr...@twitter.com > >wrote: > > > > >> You'll almost certainly want to change the password on that account > > >> immediately, as the basic auth header is easily decrypted. > > > > >> ---Mark > > > > >>http://twitter.com/mccv > > > > >> On Fri, Mar 19, 2010 at 9:20 AM, Oli <oliverst...@gmail.com> wrote: > > > > >>> 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. > > 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. > 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.
