[
https://issues.apache.org/jira/browse/HDFS-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217605#comment-13217605
]
Tsz Wo (Nicholas), SZE commented on HDFS-3006:
----------------------------------------------
> Nicholas, doesn't this imply webhdfs and httpfs are now incompatible? Maybe
> you could at least file a jira so we do fix it if you don't have time to fix
> it here?
The specification does not specify the Content-Type for empty responses. So
the Content-Type could be anything, provided that he response is valid. For
HttpFs, It is very likely that it has such bug. Filed HDFS-3018 as a task to
check it.
> Webhdfs "SETOWNER" call returns incorrect content-type
> ------------------------------------------------------
>
> Key: HDFS-3006
> URL: https://issues.apache.org/jira/browse/HDFS-3006
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.2
> Reporter: bc Wong
> Assignee: Tsz Wo (Nicholas), SZE
> Fix For: 0.24.0, 1.1.0, 0.23.2, 1.0.2
>
> Attachments: h3006_20120223.patch, h3006_20120224.patch,
> h3006_20120224b.patch, h3006_20120224c.patch, h3006_20120224c_branch1.patch
>
>
> The SETOWNER call returns an empty body. But the header has "Content-Type:
> application/json", which is a contradiction (empty string is not valid json).
> This appears to happen for SETTIMES and SETPERMISSION as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
