Re: Apache & VirtualHosts
From: R.Gunn (rgunn_at_stephenaustinNOSPAM.co.uk)
Date: Mon, 21 Jul 2003 10:13:14 +0000 (UTC)
I see big circles approaching! ;o)
The problem I have is not so much the port numbering issue; I understand
that - but why force https on port 81 when I want http on port 81. Yes the
config file says to listen on port 81 - but not for https - for http. I
never changed 443 to 81 at all.
And, why only to the https enforcement when I turn name based virtual hosts
on - why not do it all the time.
I never had this problem configuring virtual hosts in Apache for Win32
(running WIndows2000) - the only problem there was file path for some
reason - I had to get rid og the var/www or (whatever it was then) and
replace with full c:\inetpub\wwwroot\apache\... path (don't know why - but
it worked after that!)
Cheers! (more help please!!?)
"Maurits van de Kamp" <firstname.lastname@example.org> wrote in message
> R.Gunn wrote:
> > If I do http://shrike:81 I get the "bad request" page above telling me
> > use https://shrike:81 - which is very confusing as https:// should be
> > 443 surely. If I then do visit https://shrike:81 I do get my "root"
> > index page I created.
> It's not that confusing.. "https" really means something else than
> (just) the port. https:// tells your browser to use the secure
> http-protocol instead of the normal one. *By default*, the https service
> listens on port 443 (just like normal http listens to port 80 by
> default). But if you put it on port 81, it's on 81.
> So, https://shrike:81 tells your browser to use the https protocol and
> try it on port 81. https://shrike tells the browser to use https
> protocol on port 443. http://shrike:81 tells the browser to use the
> *normal* http protocol on 81. http://shrike tells the browser to use the
> normal http protocol on port 80.
> See? :)