--- Tommy McNeely <[EMAIL PROTECTED]> wrote:
> but then ... if you have an IP for each SSL site, it
> doesnt make much sense
> to name based host it on HTTP :)
No, but I if you only had 2 or 3 addresses and you had
to host 40 or 50 sites and only 1 or 2 needed ssl to
work, then you could mix nam
WOW!
you have a really good point..
name base host the domain on HTTP .. then have a different HTTPS port for
each site.. and the only doc on the HTTP site would be a meta redirect to
the correct https://server.domin:4431/ type site
Tommy
--On Friday, January 17, 2003 03:19:46 PM -0800 Gordon
but then ... if you have an IP for each SSL site, it doesnt make much sense
to name based host it on HTTP :)
Tommy
--On Friday, January 17, 2003 02:34:31 PM -0800 Kevin McConnell
<[EMAIL PROTECTED]> wrote:
--- Dax Kelson <[EMAIL PROTECTED]> wrote:
What do you mean by "name based" versus "reg
On Fri, 2003-01-17 at 13:52, Dax Kelson wrote:
> Therefore, virtual hosting
> SSL sites requires the use of unique IP addresses for each site."
Unique port numbers work as well, and are in far greater supply than
unique IP addresses. :)
--
Psyche-list mailing list
[EMAIL PROTECTED]
https://
--- Dax Kelson <[EMAIL PROTECTED]> wrote:
> What do you mean by "name based" versus "regular
> name based"?
Sorry, I mean that you can't mix name based virtual
hosts with ssl. You could on the other hand use named
based virtual hosts for regular http connections and
use ip based virtual hosts for
AGREED!
The way I get around that is to "make" my certificate for just domain.com
.. then have all my virtual hosts like mail.domain.com and admin.domain.com
or whatever else... all ofcourse only use the domain.com cert file,
however, with a cert for domain.com and a hostname of mail.domain.com
On Fri, 17 Jan 2003, Kevin McConnell wrote:
> I wanted to do the same, but according to apache.org, under apache 2.0
> you can't mix name based virtual hosting and regular name based virtual
> hosting. Only one will work.
> http://httpd.apache.org/docs-2.0/vhosts/name-based.html
What do you mean
On Fri, 2003-01-17 at 21:39, Kevin McConnell wrote:
> --- "Mr. Adam ALLEN" <[EMAIL PROTECTED]>
> wrote:
>
> > This virtual host is repeated three different times
> > with different
> > server names, Apache is delivering the right
> > contents out of the right
> > directories for the Server Name's,
On 17 Jan 2003, Mr. Adam ALLEN wrote:
> I'm experiencing problems with Apache, doing name based virtual hosting
> for SSL sites.
This is not possibleIn fact, I just wrote about it.
"The HTTPS protocol requires that an SSL handshake occur as the very first
step. During the SSL handshake the w
--- "Mr. Adam ALLEN" <[EMAIL PROTECTED]>
wrote:
> This virtual host is repeated three different times
> with different
> server names, Apache is delivering the right
> contents out of the right
> directories for the Server Name's, it's just the SSL
> Certificates which
> are getting confused (The
On Friday 17 January 2003 21:04, Mr. Adam ALLEN wrote:
> ServerName files.mydomain
try:
ServerName files.mydomain:443
else check the apache migration document:
http://www.redhat.com/docs/manuals/linux/RHL-8.0-Manual/ref-guide/s1-httpd-v2-mig.html
--
Psyche-list mailing list
[EMAIL PROTECTED]
11 matches
Mail list logo
