Message325973
Please note that SSL_verify_client_post_handshake() doesn't perform any IO by itself.
A typical scenario for HTTP looks like this (actual flow may vary):
* client
* send ``HTTP GET /path``
* server
* recv
* verify_client_post_handshake
* send HTTP Connection Upgrade (emits CertRequest message)
* client
* recv
* send upgrade confirmation (emits Certificate, CertificateVerify, Finish message)
* server
* recv
* verify certificate
* send payload or error (may emit TLS alert for unknown, invalid, or missing cert)
* client
* recv (receive TLS alert or server response) |
|
Date |
User |
Action |
Args |
2018-09-21 08:00:36 | christian.heimes | set | recipients:
+ christian.heimes, benjamin.peterson, ned.deily |
2018-09-21 08:00:36 | christian.heimes | set | messageid: <1537516836.06.0.956365154283.issue34670@psf.upfronthosting.co.za> |
2018-09-21 08:00:36 | christian.heimes | link | issue34670 messages |
2018-09-21 08:00:35 | christian.heimes | create | |
|