Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 8 Jul 2015 19:21:04 +0000 (UTC)
From: "Gil Vernik (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12843612.1436383207000.133792.1436383264585@Atlassian.JIRA>
In-Reply-To: <JIRA.12843612.1436383207000@Atlassian.JIRA>
References: <JIRA.12843612.1436383207000@Atlassian.JIRA>
 <JIRA.12843612.1436383207434@arcas>
Subject: [jira] [Created] (HADOOP-12208) Wrong token in the authentication
 header when there is re-authentication request
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Gil Vernik created HADOOP-12208:
-----------------------------------

             Summary: Wrong token in the authentication header when there is re-authentication request
                 Key: HADOOP-12208
                 URL: https://issues.apache.org/jira/browse/HADOOP-12208
             Project: Hadoop Common
          Issue Type: Bug
          Components: fs/swift
    Affects Versions: 2.6.0
            Reporter: Gil Vernik
            Assignee: Gil Vernik
             Fix For: 2.7.2


When authentication token expires, Swift returns 401. In this case the exec method from SwiftRestClient catches this exception and performs another authentication request to renew the token. If authentication successful, exec method retry original request. However, the bug is that retry still uses old token in a header and doesn't update it with a new one.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)