[jira] [Updated] (HADOOP-8816) HTTP Error 413 full HEAD if using kerberos authentication

["Moritz Moeller (JIRA)" <ji...@apache.org>]

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

Moritz Moeller updated HADOOP-8816:
-----------------------------------

    Attachment: hadoop-common-kerberos-increase-http-header-buffer-size.patch

attached is a patch that changes the header buffer size to 64kb.

32kb is the highest suggested value that I found in the following pages that deal with the same problem:
https://issues.alfresco.com/jira/browse/ALF-13810
https://issues.apache.org/bugzilla/show_bug.cgi?id=42003

I know no disadvantages of a higher header buffer size limit.


                
> 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
>         Attachments: hadoop-common-kerberos-increase-http-header-buffer-size.patch
>
>
> 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