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
The package seems intended for channel auth and not for an arbitrary HTTP endpoint. So it seems to assume it will look for a repo.xml etc which wouldn't be there on a proxy.
If auth is intended to be the handler for 407s and not just avoiding 403s than guessing there needs to be a path similar to curl where you have a -u and a -U handler since you will have an auth for the destination and possibly something in the middle.
The text was updated successfully, but these errors were encountered:
I can imagine us adding the the extra options like you suggested. My proposal would be something like --proxy-user and --proxy-password.
You also bring a up a good point about having an option to apply a particular authentication scheme to all channels and not only that but being able to apply multiple authentication schemes at once. Because these are ultimately just separate HTTP headers, this shouldn't be that difficult.
I will go back to the drawing board and see how we might elegantly support this 😌.
What happened?
Conda Info
Conda Config
Conda list
Additional Context
connecting back to conda/conda#12013
The package seems intended for channel auth and not for an arbitrary HTTP endpoint. So it seems to assume it will look for a repo.xml etc which wouldn't be there on a proxy.
If auth is intended to be the handler for 407s and not just avoiding 403s than guessing there needs to be a path similar to curl where you have a -u and a -U handler since you will have an auth for the destination and possibly something in the middle.
The text was updated successfully, but these errors were encountered: