A Clearer view on Name Based Virtual Hosts

[theskink]

Hello,,,

I have been running a little server for about 5 years on windows,,, about 1 year with Xampp... It seems to me that named based VHosts are exploited in a particular way...

Explanation: VHosts were in the httpd file and now is in a extra file but this oddity remains in both configs... VHost are being used to exploit a main host "default"...

example: http://www.NamedBasedVHost.com/Mainserver-page.htm

I see these exploits in the logs and when I follow these type links I am not able to browse that VHost site again till I clear my cache... I cant even get to one VHost at all from the host computer...

I realize these may be Apache issues but I cant find a answer...

2... Is there a way to ensure that one cannot go to a default server page via a Vhost which I would hope to be a separate entity...

In past configs I would have my NameBased VHost folder in htdocs but in Xampp I have NameBased VHost folder in the same folder as htdocs,,, I wonder if I have this wrong and VHosts folders belong in the htdocs folder...

I have a router and a small windows network... Is there a way to assign ip ex. 192.168.1.35 to a VHosts via my Linksys router??? I never pursued another avenue as NameBased was to easy...

Since I wrote this I have more disturbing results on NameBasedvhosts... My main site is being spidered by search engines as the results for a VHost.





Thank you for this product and more important maintaining it...