Hello Andrew, The requests are done via some other long-running program issuing thousands(?) of PUTs, and the problem shows up randomly - I don't know the exact stimulus that causes the 401 occurrences. Issuing CURL requests in an attempt to trigger the 401 would take a looooong time :)
I believe the RetryOnRenew mechanism is NOT invoked because I have logged authentication renewals and they are very straightforward. (I find myself unable to get wireshark pcaps of the problem despite them occurring during an active capture... ???) On Tue, Oct 28, 2014 at 10:17 PM, Andrew Phillips <[email protected]> wrote: > Is there a way to force the headers for these 401 responses to be logged? >> > > I'm afraid I can't help with that, but does making the request that > jclouds makes via cURL actually cause a 401, or does it succeed when not > going via jclouds? > > Regards > > ap > -- Daniel Hsueh -- mailto:[email protected] <[email protected]> tel:+1-905-287-2167
