Message216680
| Author |
pitrou |
| Recipients |
Ye.Wang, christian.heimes, dstufft, giampaolo.rodola, janssen, pitrou |
| Date |
2014年04月17日.09:57:05 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1397728625.77.0.116033435415.issue19500@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The RFC is unhelpfully lousy. It's not enough to process a "522" error, since that can be triggered for different reasons. You also somehow have to interpret the error text to detect that session reuse is indeed mandated by the server.
Regardless, to progress with this we would first need to implement client-side SSL session reuse, which necessitates a bunch of additional APIs (since which session is to be reused is a decision made by user code), and a new opaque type to carry SSL_SESSION objects...
(see issue #8106) |
|