that would answer to why nathanwainwright.com would work... but not the
other one.....
hrm... probably should use the servers IP ... instead of 127.0.0.1 ....
grah. tomorow. its 2am.
bogi wrote:
No
apache should run standalone, no inetd please.
What he ment is: setup your main site as a virtual host, just like he
explaind, and if you make that site the first virtual host in the config
file, then your server will respond with that site if someone accesses your
server with no host header (ie http 1.0 or just an ip-address).
Cheers
Szemir
On August 4, 2004 01:37, Nathan wrote:
K, I do have apache running standalone... would the option of inetd be
a better idea? and what else would i need to setup?
Also, where would I find some info on setting up the system like your's is?
At this point i'll try anyways.
thanks very much.
-- nathan
Shawn wrote:
Your config file should have a line like so:
NameVirtualHost *
If you use a *, you're saying that all incoming (destination) IPs will be
checked to see if they are to be handled by a virtual host. This is done
by the <VirtualHost> directives like so:
<VirtualHost *>
Using a * here says that all requests (and all ports) will be compared
against the server name and/or alias. So, a full <VirtualHost> directive
might look like so:
<VirtualHost *>
ServerName www.mysite.com
ServerAlias mysite.com
DocumentRoot /home/www
</VirtualHost>
By replacing the astrix in the VirtualHost directive, you can have Apache
only respond as the virtual host if the request is for a specific IP
address and/ or port (i.e. <VirtualHost 192.168.0.1:8080>.
I would guess from your description, you are trying to mix a standalone
server with virtual hosting. This can be done, but this is the type of
area where you might need to mess around with the value for the
NameVirtualHost.
I found it easier to setup my main site as a virtual site - so every site
on my server is a virtual site, and by relying on the requested host
name, all improper requests are handled by my default (i.e. first)
virtual host. (I'm sure the Apache Guru's on the list will likely
correct me on some points, but this is how my server is working....)
With regards to OSX, I don't think the problem would be platform specific,
but is likely more in the config file for the Virtual Hosts. However,
I've never set up Apache on a Mac before, so take this post with a grain
of salt.. :D
HTH
Shawn
On Wednesday 04 August 2004 00:22, Nathan wrote:
anyone on the list ever setup virtual hosting with apache, on OSX?
if so, some help.
I setup things with Netinfo Manager, and then /etc/httpd/httpd.conf
no avail... can't see anything locally now.
any ideas, most helpful
-- nathan
_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
|
_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
