[
https://issues.apache.org/jira/browse/HDFS-9711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122598#comment-15122598
]
Chris Nauroth commented on HDFS-9711:
-------------------------------------
I'm not aware of any way for an HTTP redirect response to tell the client to
add another custom header before sending the second request (aside from setting
a cookie). Even if there was a way, it would defeat the intent of blocking the
request. Something like a malicious HTML form using POST would pick up the
header on the redirect and then succeed.
This has been made configurable for backwards-compatibility with clients that
might not be prepared to deal with the custom header.
> Integrate CSRF prevention filter in WebHDFS.
> --------------------------------------------
>
> Key: HDFS-9711
> URL: https://issues.apache.org/jira/browse/HDFS-9711
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: datanode, namenode, webhdfs
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-9711.001.patch, HDFS-9711.002.patch
>
>
> HADOOP-12691 introduced a filter in Hadoop Common to help REST APIs guard
> against cross-site request forgery attacks. This issue tracks integration of
> that filter in WebHDFS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
