8000 `TokenAuth.get_auth_header` returns invalid data when token is `None` · Issue #182 · oras-project/oras-py · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

TokenAuth.get_auth_header returns invalid data when token is None #182

New issue

Have a question about this project? Sign 8000 up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Meallia opened this issue Mar 20, 2025 · 2 comments · Fixed by #183
Closed

TokenAuth.get_auth_header returns invalid data when token is None #182

Meallia opened this issue Mar 20, 2025 · 2 comments · Fixed by #183

Comments

@Meallia
Copy link
Contributor
Meallia commented Mar 20, 2025

When connecting to a registry for the first time, without a bearer token, the following Authorization header is sent : Bearer None. It seems to break some registry ( Jfrog's Artifactory in our case ) and make them reply with and invalid auth header.

I checked and neither docker, cri-o, podman nor flux sends an empty authorization header.

@vsoch
Copy link
Contributor
vsoch commented Mar 21, 2025

That's strange - is that documented anywhere?

@Meallia
Copy link
Contributor Author
Meallia commented Mar 21, 2025

it seems to have been caused by #148.

before this refactor, no Authorization header were sent when there was no token. Probably an oversight since it seems to be working on most public container registries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants
0