[
https://issues.apache.org/jira/browse/HDFS-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149137#comment-15149137
]
Haohui Mai commented on HDFS-7766:
----------------------------------
Sorry for the confusion. In your patch the POST request will be redirected to
DN as well so there is no blocking there.
What I proposing is that it might just make sense to do it all in the NN since
NN / DN are in different origins and it is annoying to get around for all
browsers. This is one of the main reason why the previewing feature is disabled
in the HTML5 UI.
bq. A custom header is just as easily set as a parameter to the REST URL, so I
don't see what that buys us in terms of security.
It's not about security but it's about explicitly tagging there is no backward
compatibility guarantee on the endpoint. The endpoint is only used by the UI.
> Add a flag to WebHDFS op=CREATE to not respond with a 307 redirect
> ------------------------------------------------------------------
>
> Key: HDFS-7766
> URL: https://issues.apache.org/jira/browse/HDFS-7766
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Attachments: HDFS-7766.01.patch, HDFS-7766.02.patch,
> HDFS-7766.03.patch, HDFS-7766.04.patch, HDFS-7766.04.patch, HDFS-7766.05.patch
>
>
> Please see
> https://issues.apache.org/jira/browse/HDFS-7588?focusedCommentId=14276192&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14276192
> A backwards compatible manner we can fix this is to add a flag on the request
> which would disable the redirect, i.e.
> {noformat}
> curl -i -X PUT
> "http://<HOST>:<PORT>/webhdfs/v1/<PATH>?op=CREATE[&noredirect=<true|false>]
> {noformat}
> returns 200 with the DN location in the response.
> This would allow the Browser clients to get the redirect URL to put the file
> to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
