Merge lp:~vila/bzr/1606203-long-auth into lp:bzr/2.7
| Status: | Merged |
|---|---|
| Approved by: | Richard Wilbur on 2016-09-13 |
| Approved revision: | 6617 |
| Merged at revision: | 6617 |
| Proposed branch: | lp:~vila/bzr/1606203-long-auth |
| Merge into: | lp:bzr/2.7 |
| Diff against target: |
41 lines (+12/-1) 2 files modified
bzrlib/tests/test_http.py (+10/-0) bzrlib/transport/http/_urllib2_wrappers.py (+2/-1) |
| To merge this branch: | bzr merge lp:~vila/bzr/1606203-long-auth |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Richard Wilbur | 2016-09-09 | Approve on 2016-09-13 | |
| Colin Watson (community) | Approve on 2016-09-09 | ||
|
Review via email:
|
|||
Commit Message
Fix lp:1606203 caused by using a user/pass combination for http auth longer than ~57 chars. (Vincent Ladeuil)
Description of the Change
This fixes bug #1606203 caused by using a user/pass combination for http auth longer than ~57 chars.
| Richard Wilbur (richard-wilbur) wrote : | # |
| Colin Watson (cjwatson) wrote : | # |
str.encode(
base64.encodestring exists to encode strings according to RFC 1521's base64 Content-
| Richard Wilbur (richard-wilbur) wrote : | # |
@Colin, thanks for the explanation.
@Vincent, thanks for the patch.
+1
| Richard Wilbur (richard-wilbur) wrote : | # |
sent to pqm by email

Vincent, What did the problem turn out to actually involve? Was it credentials "longer than ~57 chars" as the bug says or "creating a header value with an embedded '\n'" as a comment in the patch says? Or was it a combination of the two?
If it was the embedded '\n', how did that get in there?