How to diagnose an unknown apache setup

You need to update you httpd-vhosts.conf to something like this:

<VirtualHost *:80>
    DocumentRoot "/Users/me/Sites/www.site1.dev"
    ServerName www.site1.dev
</VirtualHost>
<VirtualHost *:80>
    DocumentRoot "/Users/me/Sites/www.site2.dev"
    ServerName www.site2.dev
</VirtualHost>

Having each domain separately in your config allows you to have separate server options for each, e.g. Rewrite config, separate log files, etc.

Then, update your /etc/hosts and add this at the end:

127.0.0.1   www.site1.dev
127.0.0.1   www.site2.dev

This step is particurarily important as this is where your OS looks first when resolving domain names. Otherwise it will not know what www.site1.dev is.

Then simply restart the server by disabling Web Sharing and enabling it again.

To make sure your config works you can check apache logs (access_log and error_log) via Console.app (Files > /private/var/log > apache2).

A few things:

1. Apache built into OS X runs on port 80. If XAMPP couldn't start the web server erroring because port 8000 is in use, something is listening on that port already. You did one of the right things in reconfiguring XAMPP's Apache port, the other would be to find what's running on 8000 :).

2. You're using the "Bonjour" name of your server, in theory. The mysite.local name. But if it's taking more than a second to resolve, then it is obviously browsing out to the internet in order to resolve the name to an address and come back inside.

If you know how, you can take the time to investigate your Bonjour settings. If you have Wide-Area Bonjour Browsing configured, but the server on the other end is not (or is no longer), these lookup delays are not completely impractical.

The quickest fix to this problem would just be to use localhost:8080 instead of mysite.local:8080, the longer one would be to trace where exactly your DNS lookup is heading too, and determining why a multi-second lookup is occurring.