For the benefit of others...
> You can even setup Apache to ignore the IP# and just respond to
> domain names... in case you're serving things up from a cablemodem.
> Seve
I just played around with this two days ago and got it working. Being
on a cablemodem, I wanted anyone (mainly cable company) going to
the IP address to just see the dummy apache intro page. If they ever
ask, I'll just say the HTML editor I use requires port 80 for testing.
I setup the virtual NameVirtualHost to the IP address, and then have
(note that 24.xx.yy.zz is just hiding the real IP)
<VirtualHost _default_:*>
ServerName 24.xx.yy.zz
ServerAdmin [EMAIL PROTECTED]
DocumentRoot /home/httpd/bogus/
</VirtualHost>
# above takes care of any bogus/invalid attempts for unknown hosts.
<VirtualHost 24.xx.yy.zz>
ServerName 24.xx.yy.zz
ServerAdmin [EMAIL PROTECTED]
</VirtualHost>
# above catches all IP address requests, and uses all the defaults defined.
<VirtualHost www.mylocalsite.com>
ServerName www.mylocalsite.com
ServerAlias mylocalsite.com
ServerAdmin [EMAIL PROTECTED]
DocumentRoot /home/mysites/mylocalsite/public_html/
ScriptAlias /cgi-bin/ /home/mysites/mylocalsite/cgi-bin/
Options ExecCgi Includes IncludesNOEXEC SymLinksIfOwnerMatch
# User mylocalsite
# Group mylocalsite
ErrorLog logs/mylocalsite/error_log
RefererLog logs/mylocalsite/referer.log
TransferLog logs/mylocalsite/txfr.log
AgentLog logs/mylocalsite/agent.log
</VirtualHost>
# Above describes an actual hostname/domain defined.
# I commented out User/Group because it needs suexec which I haven't tried.
# If you use the logs/... example, make sure to create logs/mylocalsite/
# (I learnt that one the hard way since httpd would always fail)
Thanks... Dan.
