Header key 'Authorization' or 'authorization'

[mbohlool]

Throughout the client-python implementation, we consistently used 'authorization' as the header key. urllib3 is also using that, but in some libraries, capital "Authorization" is used. This issue is a placeholder for doing a research on this and make sure we are doing the right thing.

[SEJeff]

The correct http header is Authorization with a capital A, however most python client libs use them case insensitive (see: requests, or django's test client as examples). Also, they are case insensitive.

My preference is actually Authorization as I frequently replicate data with curl / requests manually, and that is how most apps send it or webservers respond. However, per those two rfcs, neither are wrong per-se.

[mbohlool]

I agree, it should be capital Authorization with case insensitive checks. Will add help needed label so somebody look at this (It could be me if I find the time).

[saurav-malani]

Hi @mbohlool @SEJeff. If no one is working on this issue, then I would like to work on this issue.

[roycaihw]

/assign @saurav-malani

[k8s-ci-robot]

@roycaihw: GitHub didn't allow me to assign the following users: saurav-malani.

Note that only kubernetes-client members and repo collaborators can be assigned.
For more information please see the contributor guide

In response to this:

/assign @saurav-malani

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.