Re: streams/sockets slow to close?
Re: streams/sockets slow to close?
- Subject: Re: streams/sockets slow to close?
- From: Michael Brian Bentley <email@hidden>
- Date: Fri, 15 Nov 2013 09:22:03 -0800
On 11/15/13, 2:07 AM, Quinn "The Eskimo!" wrote:
On 14 Nov 2013, at 20:04, Michael Brian Bentley <email@hidden> wrote:
Then some latent packet traffic shows up well after the close.
Can you define "well after". Are we talking milliseconds? Seconds? I'd like to try this out myself, but I need to know what I'm looking for.
Be aware that closing a TLS connection results in traffic being sent on the wire [1]. If the network has failed, or the remote peer is misbehaving, that can cause long delays between your close and the final close of the TCP connection underlying the TLS connection.
Share and Enjoy
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
[1] See the discussion of close_notify in RFC 5246.
<http://www.ietf.org/rfc/rfc5246.txt>
Up to five minutes.
I'm profiling when this does and doesn't happen for us.
We're currently SSLv2 using some relaxed settings.
-Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden