You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/09/17 18:17:08 UTC
[jira] [Commented] (HADOOP-8816) HTTP Error 413 full HEAD if using
kerberos authentication
[ https://issues.apache.org/jira/browse/HADOOP-8816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457119#comment-13457119 ]
Alejandro Abdelnur commented on HADOOP-8816:
--------------------------------------------
128K as header buffer size seems a bit too big.
Could this be related to this? http://www.novell.com/communities/node/11516/kerberos-authentication-may-fail-access-manager-identity-server-users-large-group-members
Would be possible to get the actual header size that is making things to fail?
> HTTP Error 413 full HEAD if using kerberos authentication
> ---------------------------------------------------------
>
> Key: HADOOP-8816
> URL: https://issues.apache.org/jira/browse/HADOOP-8816
> Project: Hadoop Common
> Issue Type: Bug
> Components: net
> Affects Versions: 2.0.1-alpha
> Environment: ubuntu linux with active directory kerberos.
> Reporter: Moritz Moeller
>
> The HTTP Authentication: header is too large if using kerberos and the request is rejected by Jetty because Jetty has a too low default header size limit.
> Can be fixed by adding ret.setHeaderBufferSize(1024*128); in org.apache.hadoop.http.HttpServer.createDefaultChannelConnector
--
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