Return-Path: 
 <hdfs-issues-return-152520-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A7CDD18872
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Fri, 12 Feb 2016 20:25:18 +0000 (UTC)
Received: (qmail 93761 invoked by uid 500); 12 Feb 2016 20:25:18 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 93702 invoked by uid 500); 12 Feb 2016 20:25:18 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 93669 invoked by uid 99); 12 Feb 2016 20:25:18 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Feb 2016 20:25:18 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 23F892C1F5D
	for <hdfs-issues@hadoop.apache.org>; Fri, 12 Feb 2016 20:25:18 +0000 (UTC)
Date: Fri, 12 Feb 2016 20:25:18 +0000 (UTC)
From: "Ravi Prakash (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12773930.1423596523000.40808.1455308718143@Atlassian.JIRA>
In-Reply-To: <JIRA.12773930.1423596523000@Atlassian.JIRA>
References: <JIRA.12773930.1423596523000@Atlassian.JIRA>
 <JIRA.12773930.1423596523976@arcas>
Subject: [jira] [Updated] (HDFS-7766) Add a flag to WebHDFS op=CREATE to not
 respond with a 307 redirect
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Ravi Prakash updated HDFS-7766:
-------------------------------
    Attachment: HDFS-7766.05.patch

Here's a rebased patch 

> 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)