Re: [EMAIL PROTECTED] https problem

2005-12-09 Thread Tony Di Croce
ys use the certificate from the first SSL VH to establish a session so you still get warnings.Rgds,Owen BoyleDisclaimer: Any disclaimer attached to this message may be ignored.-----Original Message-From: Tony Di Croce [mailto: [EMAIL PROTECTED]]Sent: Donnerstag, 24. November 2005 00:43To: users@ht

RE: [EMAIL PROTECTED] https problem

2005-12-07 Thread Boyle Owen
may be ignored. -Original Message- From: Tony Di Croce [mailto:[EMAIL PROTECTED] Sent: Dienstag, 6. Dezember 2005 19:04 To: users@httpd.apache.org Subject: Re: [EMAIL PROTECTED] https problem I agree it is non-optimal... But short of implementing something like user mode linux, its the best way to

Re: [EMAIL PROTECTED] https problem

2005-12-06 Thread Tony Di Croce
Any disclaimer attached to this message may be ignored.-Original Message-From: Tony Di Croce [mailto: [EMAIL PROTECTED]]Sent: Dienstag, 6. Dezember 2005 15:42To: users@httpd.apache.orgSubject: Re: [EMAIL PROTECTED] https problem Hmm...But why would the URL in the browser not match the name in th

RE: [EMAIL PROTECTED] https problem

2005-12-06 Thread Boyle Owen
essage- From: Tony Di Croce [mailto:[EMAIL PROTECTED] Sent: Dienstag, 6. Dezember 2005 15:42 To: users@httpd.apache.org Subject: Re: [EMAIL PROTECTED] https problem Hmm... But why would the URL in the browser not match the name in the SSL cert? They would match... a.com and b.com are po

Re: [EMAIL PROTECTED] https problem

2005-12-06 Thread Tony Di Croce
BoyleDisclaimer: Any disclaimer attached to this message may be ignored.-Original Message-From: Tony Di Croce [mailto: [EMAIL PROTECTED]]Sent: Donnerstag, 24. November 2005 00:43To: users@httpd.apache.orgSubject: Re: [EMAIL PROTECTED] https problem I assume a.com and b.com resolve to the

RE: [EMAIL PROTECTED] https problem

2005-11-24 Thread Boyle Owen
Di Croce [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 24. November 2005 00:43 To: users@httpd.apache.org Subject: Re: [EMAIL PROTECTED] https problem I assume a.com and b.com resolve to the same IP address. If so, https to either domain will go to :443. Remember that SSL cannot use the Hostname to dist

Re: [EMAIL PROTECTED] https problem

2005-11-23 Thread Tony Di Croce
I assume a.com and b.com resolve to the same IP address. If so, https to either domain will go to :443.Remember that SSL cannot use the Hostname to distinguish sites, so the two requests look the same to apache and so you get the first VH on IP:443.Rgds,Owen BoyleDisclaimer: Any disclaimer attache

RE: [EMAIL PROTECTED] https problem

2005-11-23 Thread Boyle Owen
> -Original Message- > From: Nadir Mahmoud [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 23. November 2005 15:52 > To: users@httpd.apache.org > Subject: [EMAIL PROTECTED] https problem > > > Hello all, > > I have two websites running in apache2 (virt

[EMAIL PROTECTED] https problem

2005-11-23 Thread Nadir Mahmoud
Hello all, I have two websites running in apache2 (virtual hosts based on ip), and jboss325, so port 443 (the ssl default port) is used by jboss , When I browse the first web site like a.com, or https://a.com, it goes to https://a.com, (which is redirect command in index.html page, It's like this: