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 | orsenthil |
|---|---|
| Recipients | orsenthil, steven.k.wong |
| Date | 2008年06月13日.02:13:24 |
| SpamBayes Score | 0.08669122 |
| Marked as misclassified | No |
| Message-id | <1213323205.95.0.510533147629.issue3094@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The HTTPSConnection class derives from HTTPConnection and the methods in the HTTPConnection assume that 1) It is either over the default HTTP port or 2) Over a different port (be it different HTTP port(8080?) or 443 for HTTPS etc) and in that case it sends the port along in the request header. Thats it. So, there is no bug here. Morever, RFC 2818 states that, for HTTPS default port is 443, but the implementation are free to choose any other ports over TLS as well. Invalid bug can be closed. Thanks. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月13日 02:13:26 | orsenthil | set | spambayes_score: 0.0866912 -> 0.08669122 recipients: + orsenthil, steven.k.wong |
| 2008年06月13日 02:13:25 | orsenthil | set | spambayes_score: 0.0866912 -> 0.0866912 messageid: <1213323205.95.0.510533147629.issue3094@psf.upfronthosting.co.za> |
| 2008年06月13日 02:13:24 | orsenthil | link | issue3094 messages |
| 2008年06月13日 02:13:24 | orsenthil | create | |