Here's a strange issue… When I use the Apigee API Console to make a request, it throws a 400 Bad Request error (example<https://apigee.com/console/apigee-console-snapshots-1304226000000_bc5252c1-2e88-49e1-a1ed-550494434a7b/rendersnapshotview>), unless I define the User-Agent header (example<https://apigee.com/console/apigee-console-snapshots-1304226000000_e92d06c2-29aa-4f22-86b1-aed8c5be8c9d/rendersnapshotview>). This seems to happen on our production boxes but not on our dev/qa machines.
The only difference between those setups is that prod is whitelisted, though I wouldn't expect that to affect the search API in any way. Any ideas what's happening? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk