@ahrasis You're frequently much too quick to critize and dismiss. This was not a hijaack, I was providing an example of a scenario that controllably reproduces the symptoms that Thom describes. I use WordPress extensively and found what I thought was the same issue before installing it in the sites alphabetically around the problem site and with no other apparent cache issues. @Th0m said "Seems like the logged in WP user was coincidence." A linked similar issue was resolved with a reboot. I said I rebooted and can still reproduce the issue. I am not crossing HTTP/HTTPS. And this is not a custom-conf. I am using the software as designed using fields providing in configuration screens and according to the documentation. This allows me to confirm the existing docs and to make notes for new ones. I gladly accept that the two issues that I relate are not the same as Thom's: incorrect document root and cross-site execution. I also gladly accept when I have made errors. Nevertheless I am having these issues in a default environment. I have verified a defect in docroot assignment, and I offered this information about apache serving the wrong vhost in a thread that the OP titled "apache serving the wrong vhost". Really! Leave the attitude at the door.