Ive written a Twitter client library in Scala (a JVM-based object/functional language) that uses Apache HttpClient to connect to the Twitter servers, but now (while at a conference here in Munich) the Basic HTTP authentication fails with a 401 and no other error message that I can see. The HttpClient library *seems* to be sending the right information in the right headers, and I know the authentication credentials work because I can Curl to the page successfully. (This also means that the problem, obviously, isnt Twitters fault, at least as far as I can see.)
If youve worked with the Twitter API from Apache HttpClient in Java, can you please ping me off-list? (Or, assuming the conversation isnt considered noise, on-list is fine, too.) I could use some ideas on how to successfully debug the problem Im having. One other question vis-à-vis authentication: for Basic authentication, should the realm be Twitter API (which is what Twitter sends back from a successful Curl invocation), or should it be nothing at all? Ive seen examples that do both, and would like to do the right thing, whatever that is. (It seems to make no difference with my authentication woes, either way.) Thanks! Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writing <http://www.tedneward.com> http://www.tedneward.com
