[ 
https://issues.apache.org/jira/browse/HADOOP-18120?focusedWorklogId=772726&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-772726
 ]

ASF GitHub Bot logged work on HADOOP-18120:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/May/22 08:52
            Start Date: 20/May/22 08:52
    Worklog Time Spent: 10m 
      Work Description: 9uapaw commented on PR #4300:
URL: https://github.com/apache/hadoop/pull/4300#issuecomment-1132649285

   Looks good to me approved, thanks for the change @jacktheone. Committed to 
trunk.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 772726)
    Time Spent: 1h 20m  (was: 1h 10m)

> Hadoop auth does not handle HTTP Headers in a case-insensitive way
> ------------------------------------------------------------------
>
>                 Key: HADOOP-18120
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18120
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: auth
>            Reporter: Daniel Fritsi
>            Priority: Critical
>              Labels: pull-request-available
>         Attachments: HADOOP-18120-002.patch, HADOOP-18120-003.patch, 
> HADOOP-18120.patch
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> According to [RFC-2616|https://www.ietf.org/rfc/rfc2616.txt] HTTP Headers are 
> case-insensitive. There are proxies / load balancers (e.g.: newer versions of 
> HA-proxy) which deliberately make some of the HTTP headers lower-case results 
> in an authentication / authorization failure inside the Hadoop codebase.
> I've created a small patch (I'm from Cloudera):  
> [^hadoop-auth-headers.patch]. This resolves our authentication issue. Can 
> someone please have a look at this?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to