VirtualHost Directive with not working as expected
1 post
• Page 1 of 1
- Moritz Haslhofer
- Posts: 1
- Joined: 04 Apr 2013, 14:35
VirtualHost Directive with not working as expected
Dear community,
i try to use the VirtualHost directive on websites using different IP Addresses (but the same port).
i added just these lines to the standard installation (httpd.conf) (no htaccess files or any web.config entries other than what the installer did)
Expecting
- http://192.168.50.4/ to return 302 Forbidden
- http://192.168.50.12/ to return the Default-Document
But both sites returned 302 Forbidden
when i change the order of those entries to:
both sites return the default document.
To test my problem i created a vanilla 2008R2 Windows Server with a default IIS Installation, added a 2nd Website - pointing to inetpub\wwwroot
installed helicon-ape 3.1.0.99 (unregistered for 45days - but the persists after entering valid registration keys)
Both websites are bound to exactly one ip-address (192.168.50.4:80 and 192.168.50.12:80)
Did I miss something?
Thanks in advance,
Moritz
i try to use the VirtualHost directive on websites using different IP Addresses (but the same port).
i added just these lines to the standard installation (httpd.conf) (no htaccess files or any web.config entries other than what the installer did)
- Code: Select all
RewriteEngine off
<VirtualHost 192.168.50.4:80>
RewriteEngine on
RewriteRule .* - [F]
</VirtualHost>
<VirtualHost 192.168.50.12:80>
RewriteEngine off
</VirtualHost>
Expecting
- http://192.168.50.4/ to return 302 Forbidden
- http://192.168.50.12/ to return the Default-Document
But both sites returned 302 Forbidden
when i change the order of those entries to:
- Code: Select all
RewriteEngine off
<VirtualHost 192.168.50.12:80>
RewriteEngine off
</VirtualHost>
<VirtualHost 192.168.50.4:80>
RewriteEngine on
RewriteRule .* - [F]
</VirtualHost>
both sites return the default document.
To test my problem i created a vanilla 2008R2 Windows Server with a default IIS Installation, added a 2nd Website - pointing to inetpub\wwwroot
installed helicon-ape 3.1.0.99 (unregistered for 45days - but the persists after entering valid registration keys)
Both websites are bound to exactly one ip-address (192.168.50.4:80 and 192.168.50.12:80)
Did I miss something?
Thanks in advance,
Moritz
1 post
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 5 guests