IE can have problems with Verisign global certs if the host name you're
using in the URL doesn't match the site name in the certificate. When this
occurs you get the misleading "Server Not Found..." error.
Although not a practical solution, you can make IE work by checking "Check
for server cert
The problem with IE can occur if the server closes the idle connection
first. In your sniffs which end closed the connection?
> -Original Message-
> From: Igor Plotnikov [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 07, 2001 4:07 PM
> To: [EMAIL PROTECTED]
> Subject: KeepAlive and IE
You normally need to configure Apache to turn off persistant connections
under HTTPS for IE. This is to avoid a bug in IE where the browser asumes
the connection is still there even if the server has timed it out and closed
it. When this occurs IE throws up an incorrect error message saying there
IE is closing the connection after the handshake has successfully completed.
It can do this if the address you're using to access the site doesn't match
the address within the certificate.
-Original Message-
From: Brendon Maragia
To: [EMAIL PROTECTED]
Sent: 11/14/00 5:54 AM
Subject: Re: M
Local Director supports SSL3 sticky sessions so if you're just using SSL3 LD
will send requests with SSL sessions back to the original server that the
load balancer picked. It doesn't handle SSL2 at all in this configuration
though and you'll end up seeing error pages in the browser.
If you do ne
MS knowledge base claims it's a bug in 3.0 that was fixed in 4.0 and up.
Unfortunately they're wrong. I've seen it in 4 - 5. Not sure about 5.5 yet.
> -Original Message-
> From: David Rees [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 20, 2000 12:37 PM
> To: '[EMAIL PROTECTED]'
> Sub
Internet Explorer behaves terribly when using keep-alive connections over
HTTPS. After downloading a page it sometimes assumes the connection to the
server is still open, even if the server has timed it out and closed it.
When it tries to reuse the connection it will throw up a spurious error page
Does the address you're using to access the site match the site name in the
certificate? IE chokes with some SGC certificates if it doesn't. You can
turn off this behavior in IE by checking "Check for server certificate
revocation" in the advanced security settings.
> -Original Message-
>
> that error
> when going to other sites with a Verisign cert using IE?
>
> - Bob
>
> > -Original Message-
> > From: Wallace, William [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, July 27, 2000 10:17 AM
> > To: '[EMAIL PROTECTED]'
> > Su
Does changing the "Check for server certificate revocation (requires
restart)" advanced security setting in IE change the behavior?
> -Original Message-
> From: Burns, Robert [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 26, 2000 10:38 AM
> To: '[EMAIL PROTECTED]'
> Subject: MSIE *Ag
I've an unusual problem with IE5.00.2919.6307 (and IE5.5 as well) in
combination with a new certificate from Verisign. SSL works for every other
browser and with the problem browser when older certificates (or
certificates from a different CA) are used. In the browser settings checking
"Check for
11 matches
Mail list logo
