I have the next apache virtualhosts and NameVirtualHost settings:
NameVirtualHost 10.100.106.89
<VirtualHost 10.100.106.89>
DocumentRoot /var/www/html/dev/novared_soporte/branches/v0.3/soporte
ServerName 10.100.106.89
</VirtualHost>
<VirtualHost 10.100.106.89>
DocumentRoot /var/www/html/phpmyadmin
ServerName 10.100.106.89/phpmyadmin
Serve
I have problems with apache on MAC OS Lion 10.7.5.
I have VirtualHosts:
<VirtualHost *:80>
ServerName devel.dev
DocumentRoot /var/www
</VirtualHost>
<VirtualHost *:80>
ServerName test.dev
DocumentRoot /var/www
<Directory "/var/www">
Options Indexes FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</
I apologize if this has been asked before, but I've looked at a number of questions here and none of them seem to answer my question.
I have a series of domains all pointing to my server.
What is wrong here?
NameVirtualHost *:80
<VirtualHost _default_:80>
ServerName domain1.com
DocumentRoot /var/www/html/domain1-com
</VirtualHost>
<VirtualHost *:80>
ServerName domain2.com
ServerAlias www.domain2.com
DocumentRoot /var/www/html/domain2-com
</VirtualHost>
Problem:
domain1.com correctly serves the content at /var/www/html/domain1-com, b
I've finally made the switch to Lion but I'm having trouble setting up an Apache VirtualHost.
I want to offer custom subdomains for my customers.
According to the docs https://help.ubuntu.com/10.04/serverguide/httpd.html i have done following:
a) DNS to IP
$ echo "127.0.0.1 a" > /etc/hosts
b) Apache virtualhost
$ ls
1 2 default default.backup default-ssl
$ cat 1
<VirtualHost *:80>
ServerName a
ServerAlias a
DocumentRoot /var/www/html/a/public
<Directory /var/www/html/a/public>
#AddDefaultCharset utf-8
Di
I have configured Apache to load KnowledgeTree (KT) through a subdomain.
# Part of http.conf file
NameVirtualHost *:80
<VirtualHost *:80>
ServerName www.example.com
ServerAlias example.com
DocumentRoot /usr/local/apache2/htdocs
</VirtualHost>
<VirtualHost *:80>
ServerName knowledgetree.example.com
DocumentRoot /usr/local/apache2/htdocs/knowledgetree
</Vi
If I understand the concept of NameVirtualHost correctly it works by reading the Host variable of every HTTP request and matching it to a ServerName in any active VirtualHost directive with the matching interface and port. If it finds a matching ServerName the content of this VirtualHost is served to the client.
The Host variable can be easily forged by a client.