To follow up: I switched to a GET request, despite the docs saying "Use a POST request header parameter to avoid long URLs.". This seems to have resolved the issue. Why change now?
- Josiah -- 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
