Comment 14 for bug 437165

We have two problems here.

1: under some circumstances the oauth dance results in a 502 from the server. This is likely a configuration issue that needs to be fixed, perhaps by adding a cache exception for the /oauth path (thanks, jdo)

2: the http-client code should complain about the HTTP status instead 1) trying to interpret the body of the response, and 2) then trying again. (thanks Chad)