A 401 error should result in re-authenticating for a new token

This commit is contained in:
Zack Shoylev 2013-07-09 14:04:08 -05:00 committed by Andrew Gaul
parent 60e9062894
commit 833f046a5c
2 changed files with 3 additions and 3 deletions

View File

@ -64,8 +64,8 @@ public class RetryOnRenew implements HttpRetryHandler {
retry = false;
} else {
byte[] content = closeClientButKeepContentStream(response);
//TODO: what is the error when the session token expires??
if (content != null && new String(content).contains("lease renew")) {
// Error when the session token expires: HTTP/1.1 401 Unauthorized, no body (or provider-specific response body)
if (content != null) {
logger.debug("invalidating authentication token");
authenticationResponseCache.invalidateAll();
retry = true;

View File

@ -53,7 +53,7 @@ public class RetryOnRenewTest {
cache.invalidateAll();
expectLastCall();
expect(response.getPayload()).andReturn(Payloads.newStringPayload("token expired, please renew")).anyTimes();
expect(response.getPayload()).andReturn(Payloads.newStringPayload("")).anyTimes();
expect(response.getStatusCode()).andReturn(401).atLeastOnce();
replay(command);