Re: SslSteam causes spurious http connection attempts
- From: "davidkclark" <davidkclark@xxxxxxxxx>
- Date: 29 Mar 2007 07:53:45 -0700
Thanks for your thoughts Eugene,
I understand where you are coming from with your suggestions about not
dropping the revocation check. However, as the machines involved are
not actually connected to the internet there is no possible way at all
for these requests to succeed. The system uses a self signed
certificate (certified by a self signed root certificate) entirely on
the local network only. I know this is perhaps not the recommended
setup, but surely it should be possible to make an SSL connection
between two machines not connect to the internet. I have told it not
to check the revocation list, I do not do anything with the
certificate in either of the two available callbacks.
I do not read anywhere in the SslSteam (etc.) docs that for the
connection to work the machines have to have an open route to the
internet via port 80. Indeed, the request does not fail - it just
takes 15 seconds some times. I see three SYN packets try to get out on
port 80 each time there is the 15 seconds delay. Each of these SYN
packets happen at an interval of about 5 seconds. 5 * 3 = 15.
Thanks.
.
- References:
- SslSteam causes spurious http connection attempts
- From: davidkclark
- Re: SslSteam causes spurious http connection attempts
- From: Henning Krause [MVP - Exchange]
- Re: SslSteam causes spurious http connection attempts
- From: davidkclark
- Re: SslSteam causes spurious http connection attempts
- From: Eugene V. Bobukh [MS]
- SslSteam causes spurious http connection attempts
- Prev by Date: security
- Previous by thread: Re: SslSteam causes spurious http connection attempts
- Next by thread: security
- Index(es):
Relevant Pages
|
