Just to follow up, after a bit of digging, it appears this is a documented issue with Twitter that's been showing up for a few weeks now [ http://groups.google.com/group/twitter-development-talk/browse_thread/thread/88506e01a9c1a4e4 ], [ http://groups.google.com/group/twitter-development-talk/browse_thread/thread/acdcb4baf76037c8/e0ac9745e4c9bfe9?lnk=gst&q=refresh#e0ac9745e4c9bfe9 ].
So my question is now a bit more focused; since the response IS coming from Twitter, so do I best handle this kind of response? If I simply search for this specific string, and echo it, and exit(), will http socket make the same request, pass all parameters a second time, including auth, and return the data properly via the datasource in the refresh request? If not, any ideas how I might go about handling? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
