`TokenAuth.get_auth_header` returns invalid data when token is `None` · Issue #182 · oras-project/oras-py · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: