Re: Strange behaviour in SSL request

[Sake Blok <sake () euronet nl>]

>      11 0.016260    10.205.15.30          192.168.30.54         TLSv1    Client Key Exchange, Change Cipher Spec, 
> Encrypted Handshake Message
>      12 0.029695    192.168.30.54         10.205.15.30          TLSv1    Change Cipher Spec, Encrypted Handshake 
> Message
>      13 0.322017    10.205.15.30          192.168.30.54         TCP      23015 > https [ACK] Seq=381 Ack=4550 
> Win=65492 Len=0
>      14 45.028764   10.205.15.30          192.168.30.54         TCP      23015 > https [FIN, ACK] Seq=381 Ack=4550 
> Win=65492 Len=0

This tells you that the SSL handshake is complete (assuming the Encrypted handshake messages are in deed the "finished" 
message as it should be). As the client (10.205.15.30) ACKs the final handshake message, it knows the handshake is 
complete. It just does not send a request. In the https protocol it is the client that needs to send a request before 
the server will send any data. So the problem is on the client. The network trace won't show you any more detail than 
this, you have to start debugging your client application.

Cheers,



Sake

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe