Netscape, Mozilla and https access.

Hello,
I installed apache 2.0.54 with ssl in a Sun Ultra 10 with Solaris 10.
From either Internet Explorer or Konqueror browser, the "https" to my
apache2 server works just fine.
From Netscape, Mozilla or Firefox, "https" does not works.
Any idea ?

Thanks,
Florin

In article <dfqjac$go1$1@nntp1.jpl.nasa.gov>,
Florin <fsixt@jftl.jpl.nasa.gov> wrote:

> Hello,
> I installed apache 2.0.54 with ssl in a Sun Ultra 10 with Solaris 10.
> From either Internet Explorer or Konqueror browser, the "https" to my
> apache2 server works just fine.
> From Netscape, Mozilla or Firefox, "https" does not works.
> Any idea ?

Perhaps you have the "bad" browsers set to use a proxy that is
misbehaving?

Aside from that, the phrase "doesn't work" isn't very helpful. We need
more details (like full error messages) to figure out what's happening.

Also, does the failing request get logged in the server's log? There may
be useful information there, as well.

--
Dan Wilga dwilga-MUNGE@mtholyoke.edu
** Remove the -MUNGE in my address to reply **

Thank you for answering my question!
So:
It is no Proxy involved, all computers I am talking about here streigt
connection the internet.
You are right, "doesn't work" isn't very helpful:
This is what's hapenning when I use "https://www.alpha.....":

after I got the normal certificate on the browser screen, when I
connect to the apache2 server, after clicking OK, I get the message

"Connection to www.alpha..... has terminated unexpectedly".
Using http instead of https, everything is working fine.

There is nothing in the logs regarding this failure.
Now, what I know is this:

all info regarding the ssl connection are in "ssl.conf" file, and
httpd.conf has a directive that says:

<IfModule mod_ssl.c>
Include /etc/apache2/ssl.conf
</IfModule>

it is a "string" comming for the browser (Netscape, Mozilla, FireFox)
and checked by the apache2 server (maybe User Agent?). It looks OK for
Internet Explorer and Konqueror, but not for all of the above.
I think that something in the "ssl.conf" file should be modified, but ..
... I don't know what!

This is what is going on!
Again, thank you and I wait for any idea,

Florin
Dan Wilga wrote:


>
> Perhaps you have the "bad" browsers set to use a proxy that is
> misbehaving?
>
> Aside from that, the phrase "doesn't work" isn't very helpful. We need
> more details (like full error messages) to figure out what's happening.
>
> Also, does the failing request get logged in the server's log? There may
> be useful information there, as well.
>

Florin <fsixt@jftl.jpl.nasa.gov> said:
>It is no Proxy involved, all computers I am talking about here streigt
>connection the internet.
>You are right, "doesn't work" isn't very helpful:
> This is what's hapenning when I use "https://www.alpha.....":
>
> after I got the normal certificate on the browser screen, when I
>connect to the apache2 server, after clicking OK, I get the message
>
>"Connection to www.alpha..... has terminated unexpectedly".
>Using http instead of https, everything is working fine.

I recall having seen something like this -- how recent is the
OpenSSL you're using with your Apache (as in my case the problem
was compatibility problem between OpenSSL and the browser)?

>There is nothing in the logs regarding this failure.

Enable debug logging for the SSL handling; that might contain
clues.
--
Wolf a.k.a. Juha Laiho Espoo, Finland
(GC 3.0) GIT d- s+: a C++ ULSH++++$ P++@ L+++ E- W+$@ N++ !K w !O !M V
PS(+) PE Y+ PGP(+) t- 5 !X R !tv b+ !DI D G e+ h---- r+++ y++++
"...cancel my subscription to the resurrection!" (Jim Morrison)