http auth pycurl is broken
Bug #177643 reported by
Vincent Ladeuil
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
High
|
Vincent Ladeuil | ||
Bug Description
Working on bug #175524 I discovered that auth support for pycurl is broken on several aspects:
- user is never prompted for passwords,
- authencation.conf is not supported,
- embedding user/pass in urls doesn't work anymore
Until fixed, urllib can be used instead.
Related branches
lp:~vila/bzr/bzr.integration
(Merged)
| Changed in bzr: | |
| assignee: | nobody → v-ladeuil |
| importance: | Undecided → High |
| status: | New → In Progress |
Revision history for this message
| Vincent Ladeuil (vila) wrote | #1 |
| Changed in bzr: | |
| status: | In Progress → Fix Committed |
| Changed in bzr: | |
| milestone: | none → 1.1 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We use pycurl mostly as a blackbox, so this can only be fixed partially.
Since we have no visibility on proxy handling, we can't change the way pycurl handle them. That means we can't prompt for passwords.
For the http authentication, again, pycurl doesn't provides informations about what scheme is used, what realm, etc.
Trying to work around these limitations will go against that blackbox principle.
The fix will address handling credentials embedded in the urls, which should be enough until pycurl is deprecated.