This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | kyoshidajp |
|---|---|
| Recipients | Ivan.Pozdeev, alex, artem.smotrakov, eamanu, jwilk, kyoshidajp, martin.panter, orsenthil, xtreak |
| Date | 2018年12月29日.15:02:19 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1546095739.7.0.952203446847.issue33661@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
According to RFC7235 (https://tools.ietf.org/html/rfc7235#section-4.1), WWW-Authenticate header is sent from server to client. And it has not credential data. Also, Cookie2 header is already obsoleted by RFC6295 (https://tools.ietf.org/html/rfc6265). So, I think that both "Authorization" and "Cookie" are enough. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018年12月29日 15:02:20 | kyoshidajp | set | recipients: + kyoshidajp, orsenthil, jwilk, alex, martin.panter, Ivan.Pozdeev, artem.smotrakov, eamanu, xtreak |
| 2018年12月29日 15:02:19 | kyoshidajp | set | messageid: <1546095739.7.0.952203446847.issue33661@roundup.psfhosted.org> |
| 2018年12月29日 15:02:19 | kyoshidajp | link | issue33661 messages |
| 2018年12月29日 15:02:19 | kyoshidajp | create | |