HomeSort by relevance Sort by last modified time
    Searched full:close_notify (Results 1 - 10 of 10) sorted by null

  /external/curl/lib/vtls/
schannel.c     [all...]
  /external/boringssl/src/ssl/test/runner/
common.go 774 // NoCloseNotify, if true, causes the close_notify alert to be skipped
778 // ExpectCloseNotify, if true, requires a close_notify from the peer on
779 // shutdown. Records from the peer received after close_notify is sent
    [all...]
conn.go 754 // Looking for a close_notify. Note: unlike a real
    [all...]
runner.go     [all...]
  /external/boringssl/src/ssl/
d1_pkt.c 218 * peer never received our close_notify. Report to the caller that the channel
234 * Alert records (e.g. close_notify) and out of records. */
s3_pkt.c 376 * Alert records (e.g. close_notify) or renegotiation requests. */
626 /* close_notify has been sent, so discard all records other than alerts. */
ssl_lib.c 653 /* Do nothing if configured not to send a close_notify. */
715 /* The socket was cleanly shut down with a close_notify. */
    [all...]
  /external/boringssl/src/include/openssl/
ssl.h 344 * it returns 0 if |ssl| completed uni-directional shutdown; close_notify has
345 * been sent, but the peer's close_notify has not been received. Most callers
347 * again. It returns 1 if close_notify has been both sent and received.
349 * If the peer's close_notify arrived first, the first stage is skipped.
350 * |SSL_shutdown| will return 1 once close_notify is sent and skip 0. Callers
360 * neither send nor wait for close_notify but still retain the session.
367 * enabled, |SSL_shutdown| will not send a close_notify alert or wait for one
376 * |SSL_shutdown| will not send a close_notify alert or wait for one from the
426 * was cleanly shut down with a close_notify alert. */
    [all...]
  /external/boringssl/src/ssl/test/
bssl_shim.cc     [all...]
  /external/curl/lib/
urldata.h 326 bool recv_sspi_close_notify; /* true if connection closed by close_notify */
    [all...]

Completed in 453 milliseconds