falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Balu Vellanki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-748) Falcon throws '413 Full Head' error message when kerberos is enabled with AD
Date Wed, 01 Oct 2014 23:34:34 GMT

    [ https://issues.apache.org/jira/browse/FALCON-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155784#comment-14155784

Balu Vellanki commented on FALCON-748:

The code changes look good. I submitted a new patch that has documentation for the newly added
startup property "falcon.jetty.request.buffer.size"

> Falcon throws '413 Full Head' error message when kerberos is enabled with AD
> ----------------------------------------------------------------------------
>                 Key: FALCON-748
>                 URL: https://issues.apache.org/jira/browse/FALCON-748
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.5
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>            Priority: Critical
>              Labels: security
>             Fix For: 0.6
>         Attachments: FALCON-748-v1.patch, FALCON-748.patch
> PROBLEM:  Customer has Kerberos setup with AD, and when using ambari-qa or other users
of HDP, we are able to get the required details but using the AD users receiving the exception
'413, message: FULL head'
> IMPACT:   This makes falcon unusable for replication as the AD users cannot access falcon
> 1.  Set up AD user and Kerberos pointing to AD users
> 2.  Enable Kerberos for the HDP cluster.
> 3.  Try to run the falcon admin -version command, you would see the issue.
> ACTUAL BEHAVIOR:  Receiving '413, message: FULL head' when trying to access falcon. 
> EXPECTED BEHAVIOR:   The exception should not occur.
> 1.  The reason for this exception is because of the header buffer size being limited
in our embedded Jetty for Falcon.  
> 2.  Found a blog which states what needs to be set  (http://blog.richeton.com/2010/03/11/set-jetty-buffer-size-maven/)

This message was sent by Atlassian JIRA

View raw message