[QUOTE][u]Quote by: khiltd[/u][p]Do you not have a backup of your previous configuration? It’s been my experience that Apple updates routinely trash those things beyond recognition. [/p][/QUOTE]

Alas no. I should have read the update notes to see what it was updating. That’s the hugely annoying part, no backup of this.

The fact that I change it to a random port in server admin (say 801) then check the files in /private/etc/httpd/sites and it shows *:801, then stop/start apache, then change back to 80, save, stop/start and the config file has gone to *:16080 again.

Anyone had the same problem and found an easy fix?

Thanks for that. I checked the perfcache config and saw some strangeness. I have around 15 vhosts in the config, some of which are disabled. I noticed that two of the disabled hosts had performance caching enabled, but were commented out of the config file due to the hosts being disabled in apache. Once I removed the performance caching option from the sites in the Server Admin, they disappeared from the perfcache config. I restarted the apache server and it’s now all working. So for some reason when the perf cache config had a disabled host with performance caching enabled, it was putting it on all vhosts regardless when people tried to go to a page that used mod_rewrite to fix the trailing slash issue.

Strangeness all around but your help was invaluable. Thanks again!