Hi folks, I'm seeing an issue where requests sent to search.twitter.com get a 301 redirect, but the redirected URL is identical to the original.
I think this is the exact same issue reported 3 years ago: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/65e0a0990b120abf In this case, the library I'm using constructs a Host: header that includes the port number: search.twitter.com:80. From testing with other tools, it appears that if the port number is left off, the request succeeds. Any help? Thanks, -Arthur -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
