Re: Apache & VirtualHosts

From: R.Gunn (rgunn_at_stephenaustinNOSPAM.co.uk)
Date: 07/21/03 

Date: Mon, 21 Jul 2003 10:13:14 +0000 (UTC)

>:oI

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!!?)

:)

Richard

"Maurits van de Kamp" <james.t.kirk@enterprise.nasa.gov> wrote in message
news:bfgcts$emd$1@reader10.wxs.nl...
> R.Gunn wrote:
>
>
> > If I do http://shrike:81 I get the "bad request" page above telling me
to
> > use https://shrike:81 - which is very confusing as https:// should be
port
> > 443 surely. If I then do visit https://shrike:81 I do get my "root"
html
> > 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? :)
>
> Maurits.
>

Relevant Pages

  • Re: RWW with no https
    ... Speaking about MS IIS as a web server, in HTTP, one can run multiple ... "host headers" and run all sites on the default port 80. ... to workstations, runs on port 4125, which is dynamically opened by the SBS ... HTTP why cant you do the same with HTTPS? ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW with no https
    ... Change your ports for Kerio, using the instructions he provided, or get a different static IP for RWW ... Windows Small Business Server 2008 Unleashed ... running Https, I still have http open and free to use where ever. ... >> port but going to port 8080. ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW with no https
    ... /remote is a subfolder of 'Default Web Site' and the default site on SBS ... So just so we are all clear, RWW HAS to go over HTTPS. ... Even if I do https but port 8080 would not matter ... Basically that server is ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW with no https
    ... /remote is a subfolder of 'Default Web Site' and the default site on SBS ... So just so we are all clear, RWW HAS to go over HTTPS. ... Even if I do https but port 8080 would not matter ... Basically that server is ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW with no https
    ... /remote is a subfolder of 'Default Web Site' and the default site on SBS ... So just so we are all clear, RWW HAS to go over HTTPS. ... Even if I do https but port 8080 would not matter ... Basically that server is ...
    (microsoft.public.windows.server.sbs)