Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 10 Nov 2011 01:59:52 +0000 (UTC)
From: "Arpit Gupta (Assigned) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <362284733.16282.1320890392737.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1972429672.15983.1320884152690.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (HADOOP-7812) http call when no authorization is
 sent throws a 401 with no error resonse
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-7812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arpit Gupta reassigned HADOOP-7812:
-----------------------------------

    Assignee: Arpit Gupta
    
> http call when no authorization is sent throws a 401 with no error resonse
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-7812
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7812
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 0.20.205.0
>            Reporter: Arpit Gupta
>            Assignee: Arpit Gupta
>         Attachments: HADOOP-7812.branch-0.20-security.patch
>
>
> Currently if you make an http call to the namenode and do not send any authorization returns 401 as expected but no response content.
> I would be nice if we could return some error response stating that the user provided no authorization. It would make it a little easier for people making the call from a browser to find out if something went wrong.
> curl call
> {code}
> curl -i "http://NN:PORT/webhdfs/v1/tmp/webhdfs_data?op=gethomedirectory"
> HTTP/1.1 401 Unauthorized
> Content-Type: text/html; charset=utf-8
> WWW-Authenticate: Negotiate
> Content-Length: 0
> Server: Jetty(6.1.26)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira