-
Notifications
You must be signed in to change notification settings - Fork 760
New issue
Have a question about this project? Sign 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
HTTP status client error (401 Unauthorized) / (403 Forbidden) for packages hosted on a JFrog PyPI repo #2566
Comments
zanieb
added
bug
Something isn't working
registry
Related to package indexes and registries
labels
Mar 20, 2024
Can you confirm that the Are there logs like |
Yes, Here's the install log (with redacted info)
|
Thanks! |
zanieb
added a commit
that referenced
this issue
Mar 21, 2024
Closes #2566 We were storing the username e.g. `charlie@astral.sh` as a percent-encoded string `charlie%40astral.sh` which resulted in different headers and broke JFrog's artifactory which apparently does not decode usernames. Tested with a JFrog artifactory and AWS CodeArtifact although it is worth noting that AWS does _not_ have a username with an `@` — it'd be nice to test another artifactory with percent-encoded characters in the username and/or password.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar to an issue reported at #2444, the authentication fails when trying to install packages from extra index URL pointing to a JFrog PyPI repo
uv versions where it doesn't work:
uv==0.1.19 uv==0.1.22 # current latest at the time of this issue
The issue was fixed by on v0.1.20 likely because it has the same root cause as #2444 that was fixed by #2446). But it got broken again on v0.1.22 likely due to #2449.
The text was updated successfully, but these errors were encountered: