There's also some examples in there of getting headers out while
applying a second response handler. That should get you there. If
the the redirect is expected, it might be best to do things a
differently from that and call `when` to require that the first
request return a 302, process the Location header, then get the data
you want in the next request.
On 7/23/10 3:52 PM, Gerolf Seitz [via Databinder] wrote:
Explicitly setting the HttpClientParams "handle_redirects" and
"cookie_policy" didn't help :/
Btw, I get the same behavior for non SSL requests too.