[ 
https://issues.apache.org/jira/browse/HDFS-11222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752148#comment-15752148
 ] 

Wei-Chiu Chuang commented on HDFS-11222:
----------------------------------------

I am not actually familiar with using curl to send webhdfs/httpfs requests. But 
two things I noticed in the patch:

# mkdirs request should be sent via PUT method. It can't be sent via POST 
method.
# If I send mkdirs via PUT to httpfs without Content-Type, my request is not 
rejected.
# Looking at code (CheckUploadContentTypeFilter#doFilter), this should only 
affect append and create, and when data=true. For example: 
{noformat}
curl -i --negotiate -u : -X PUT 
"http://ns1:14000/webhdfs/v1/tmp/bar3/abc?op=CREATE&data=true"; -H 
'content-type: text/html'
{noformat}
# I verified the above command passes for webhdfs. So it's interesting there's 
discrepancy between httpfs and webhdfs.

> Document application/octet-stream as required content type for HTTPFS PUT and 
> POST
> ----------------------------------------------------------------------------------
>
>                 Key: HDFS-11222
>                 URL: https://issues.apache.org/jira/browse/HDFS-11222
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: documentation, httpfs
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Sailesh Patel
>            Assignee: Yiqun Lin
>            Priority: Minor
>         Attachments: HDFS-11222.001.patch
>
>
> Documentation  at [1]   should  indicate the PUT and POST requires a command 
> like  ( --header ):
> curl -i -X PUT -T <LOCAL_FILE> 
> "http://<DATANODE>:<PORT>/webhdfs/v1/<PATH>?op=CREATE..." --header 
> "content-type: application/octet-stream"
> [1]  
> https://hadoop.apache.org/docs/stable2/hadoop-project-dist/hadoop-hdfs/WebHDFS.html#Create_and_Write_to_a_File



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to