hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4585) Webhdfs sometimes can't negotiate a SPNEGO token
Date Mon, 11 Mar 2013 21:17:12 GMT

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

Alejandro Abdelnur commented on HDFS-4585:
------------------------------------------

I don't think a SPNEGO issue but a max HTTP header issue. you could try having a servlet returning
a 'large' header to see when curl breaks (if it does) because of the header size being too
large.
                
> Webhdfs sometimes can't negotiate a SPNEGO token
> ------------------------------------------------
>
>                 Key: HDFS-4585
>                 URL: https://issues.apache.org/jira/browse/HDFS-4585
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: webhdfs
>    Affects Versions: 2.0.0-alpha, 3.0.0, 0.23.7
>            Reporter: Daryn Sharp
>
> I'm not sure if this is a curl problem or webhdfs problem, but webhdfs will reject some
users because the Authorization header is too big.  In the case below, the header contains
4041 bytes, whereas a keytab user is generating 1745 bytes.  The failed user can use webhdfs
via "hadoop fs", but not via curl.
> {noformat}
> curl -v --negotiate -u : 'http://host/webhdfs/v1/?op=GETDELEGATIONTOKEN'
> > GET /webhdfs/v1/?op=GETDELEGATIONTOKEN HTTP/1.1
> > Authorization: Negotiate <<4041 bytes>>
> > User-Agent: curl/7.19.5
> > Host: host
> > Accept: */*
> > 
> < HTTP/1.1 413 FULL head
> < Connection: close
> < Server: Jetty(6.1.26)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message