I am getting a Encryption alert from the client after the server and client have exchanged application data. The Error codes do not seem consistent between the Alert Description Types. Why would the client send an alert after several application packets have passed successfully? Thank you in advance. Dan asked 16 Jan '13, 15:58  DanS |
2 Answers:
Assuming the traffic is https, what is the order in which you see "application data". This can most easily be seen when using a filter The connection is kept open on the application level (http). So you need to look into the KeepAlive settings of the embedded server or the http settings on the client to make the session last longer. Also SSL session caching can reduce the workload on the embedded server, if it supports it. answered 17 Jan '13, 07:43  SYN-bit ♦♦ |
It is probably not an error. You will see alerts as a notification that the encrypted session is going to be terminated after the data exchange was complete, which is perfectly normal. IIRC it is designed like this to make it harder for attackers to spoof session termination packets. answered 16 Jan '13, 16:02  Jasper ♦♦ |
Thank you Jasper. We have an embedded server and the handshake is hurting our performance for the web session. Is there a way to keep the connection open? I haven't found a linger option in SSL. There is one for the socket connection which we have set, but it doesn't help if SSL is shutting the connection down. Thanks again. Dan
Is there a way to keep an SSL connection open?