[
https://issues.apache.org/jira/browse/HDFS-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954419#comment-13954419
]
Haohui Mai commented on HDFS-4564:
----------------------------------
bq. It does, but it creates an incredible noisy exception trace that reports
the failure as the response not being json.
It does not seem to me to be a blocker of 2.4. Can you please move it out to
2.5?
bq. Bottom line is AuthenticatedURL is unnecessary and introduces nothing but
problems for webhdfs. It's only useful for oozie's anon/non-anon support.
{{URLConnectionFactory}} wraps the same mechanism, and it is used implicitly in
transferring edit logs between NN and JNs, transferring fsimage between NNs,
etc. If you think that this is a no-op, it might be better to revisit
{{URLConnectionFactory}} and to clean up all the issues in one jira. Addressing
it in webhdfs only looks a partial solution to me.
In my own opinion, I don't think the above issues are blockers. Maybe we can
move forward and address them in 2.5.
> Webhdfs returns incorrect http response codes for denied operations
> -------------------------------------------------------------------
>
> Key: HDFS-4564
> URL: https://issues.apache.org/jira/browse/HDFS-4564
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: webhdfs
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Blocker
> Attachments: HDFS-4564.branch-23.patch, HDFS-4564.branch-23.patch,
> HDFS-4564.branch-23.patch, HDFS-4564.patch, HDFS-4564.patch
>
>
> Webhdfs is returning 401 (Unauthorized) instead of 403 (Forbidden) when it's
> denying operations. Examples including rejecting invalid proxy user attempts
> and renew/cancel with an invalid user.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
