Can't log in with w3m due to bad cookies
Bug #59510 reported by
Björn Tillenius
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Unassigned |
Bug Description
The textbrowser w3m treats cookies from Launchpad as bad, as per RFC 2109, section 4.3.2, rule 3, and it seems that this makes it impossible to log in. By default the cookies are rejected, but even if you accept the cookies you can't log in.
Changed in launchpad: | |
assignee: | nobody → stub |
Changed in launchpad: | |
assignee: | stub → nobody |
Changed in launchpad-foundations: | |
status: | Confirmed → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
Björn Tillenius wrote:
> Public bug reported:
>
> The textbrowser w3m treats cookies from Launchpad as bad, as per RFC
> 2109, section 4.3.2, rule 3, and it seems that this makes it impossible
> to log in. By default the cookies are rejected, but even if you accept
> the cookies you can't log in.
>
> ** Affects: launchpad (upstream)
> Importance: Untriaged
> Assignee: Stuart Bishop
> Status: Unconfirmed
>
From a brief reading, if we fix this it means that logging onto launchpad. net will mean you are not logged into launchpad.net. launchpad. net and then launchpad.net, launchpad. net.
blueprint.
Further, if you logged into blueprint.
you will have two distinct sets of session credentials and we would have to
handle this case when the user returns to blueprint.
-- www.canonical. com/ www.ubuntu. com/
Stuart Bishop <email address hidden> http://
Canonical Ltd. http://