From: Michael Crute <mcrute@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Apache Virtual Host
Date: Sat, 3 Sep 2005 20:06:52 -0400 [thread overview]
Message-ID: <558b73fb050903170652b50ae3@mail.gmail.com> (raw)
In-Reply-To: <431A2D1C.60402@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On 9/3/05, q-parser <quickparser@gmail.com> wrote:
>
> Those port numbers are chosen for explanatory reason, but I wouldn't
> object if they worked ;) This whole file is Include-d into apache2.conf. I
> emphasize that on my localhost, it works great, with ports 85 and 8585
> instead the two here. The curious thing is, that if I want to use port 8585
> here, the browser shows me main apache page (you know, as if port 80 is
> used).
> All I want to know is why apache does not 'want' to listen to the given
> ports? I don't know, maybe it does, but I'm getting time-outs.
>
>
Well you really don't need those Listen directives, those will cause the
main server to listen on those ports (thus the reason you see the main
page). You DO need NameVirtualHost directives for each port you want to
vhost on though. Try adding NameVirtualHosts for the ports and see if that
works.
-Mike
--
________________________________
Michael E. Crute
Software Developer
SoftGroup Development Corporation
Linux, because reboots are for installing hardware.
"In a world without walls and fences, who needs windows and gates?"
[-- Attachment #2: Type: text/html, Size: 1600 bytes --]
next prev parent reply other threads:[~2005-09-04 0:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 20:23 [gentoo-user] [OT] Apache Virtual Host q-parser
2005-07-28 21:25 ` Paul Raison
2005-08-07 21:21 ` q-parser
2005-08-07 23:49 ` Michael Crute
2005-08-08 0:39 ` q-parser
2005-08-08 2:53 ` Michael Crute
2005-08-08 13:01 ` A. Khattri
2005-09-03 19:55 ` q-parser
2005-09-03 20:13 ` Michael Crute
2005-09-03 23:09 ` q-parser
2005-09-04 0:06 ` Michael Crute [this message]
2005-09-04 2:13 ` q-parser
2005-09-05 2:24 ` A. Khattri
2005-09-05 3:46 ` Michael Crute
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=558b73fb050903170652b50ae3@mail.gmail.com \
--to=mcrute@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox