For serving a 46179-byte plain-text file
in the following SSL session:
Protocol : TLSv1
Cipher : EDH-RSA-DES-CBC3-SHA
(Server public key is 1024 bit)
1. Before sending a "GET / HTTP/1.0" request, I got:
SSL handshake has read 1225 bytes (i.e. 2.7% overhead),
and written 314 bytes (i.e. 0.7% overhead).
2. After sending a "GET" request, I got
47786 "read from" bytes (i.e. 3.5% overhead),
and 433 "write to" bytes (i.e. 0.9% overhead).
(See below for how I get "read from" & "write to" bytes)
Does it look about right? Please advise.
--- t c <[EMAIL PROTECTED]> wrote:
> What is the easiest way to get total bytes of ALL SSL packets
> (incoming & outgoing @ the client side) for receiving one single
> file via SSL? (i.e. original file size + SSL overhead)
> The original file is about 50K. What should be the overhead in
> size?
>
> Can I do:
>
> s_client -debug -connect XXX.com:443 ... | grep "read from"
>
> read from 08089300 [080A3000] (7 bytes => 7 (0x7))
> read from 08089300 [080A3007] (72 bytes => 72 (0x48))
> read from 08089300 [080A3000] (5 bytes => 5 (0x5))
> ...
>
> Then, add up all the bytes for INCOMING bytes.
>
> And, do
>
> s_client -debug -connect XXX.com:443 ... | grep "write to"
>
> Then add up all the bytes for OUTGOING bytes.
>
> Many thanks.
>
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
