Skip to a section of this page:

Disable XServe WEBPERFCACHE on port 16080

Mac OS X Server’s “web perfomance caching” got you down? Annoyed by seeing :16080 appear in your URLs? Here’s how to remove it:

NOTE: This entry is mostly here because I had a hard time finding instructions on how to do this at short notice, and also so that I don’t forget how it was done. My instructions are based around my experience with Mac OS X Tiger Server so… you know… UAYOR and YMMV.

Step 1: Disable webperfcache

  1. $ sudo pico /etc/hostconfig
  2. Change line WEBPERFCACHESERVER=-YES- to WEBPERFCACHESERVER=-NO-
  3. Save the file

Step 2: Update Virtual Hosts

  1. For each virtual host .conf file in /etc/httpd/sites/
  2. Change <VirtualHost *:16080> to <VirtualHost *:80>
  3. Save each file.

Step 3: Update Apache’s listening ports

  1. $ sudo pico /etc/httpd/sites/virtual_host_global.conf
  2. Change Listen *:16080 to Listen *:80
  3. Save the file

Restarting Apache $ sudo apachectl graceful should be enough to make this change stick.
If in doubt you can restart the whole XServe.

That’s it! No more port 16080 !

DISCLAIMER: WEBPERFCACHE can be helpful depending on your needs. It is my personal opinion that it shouldn’t be on by default due to the unexpected behaviours it can produce. But then Mac OS X Server is an enterprise level system, so systems administrators should be aware of what’s running on their system, expected or not.

2 Responses to “Disable XServe WEBPERFCACHE on port 16080”

Comment feeds for this post:

  1. Bo Says:
    This solution was not working for me for some reason.I am on a Xserve server running Mac OS 10.3.9. After finish all steps in this procedure, I cannot start “Web” service in Server admin. Error log indicates : “[crit] (48)Address already in use: make_sock: could not bind to address 127.0.0.1 port 80″. The fix for me is to go to every site in server admin-> Web, then go to “options”, make sure “performance cache” is off then restart the service. I have to do this for every site otherwise it won’t work.
  2. Andrew Says:
    Hi Bo. You are quite right, I can’t guarantee that this technique works with Mac OS 10.3.9, as I say this worked on an installation of Mac OS X Tiger Server (10.4). Thanks though for sharing your solution for 10.3.9.

Leave a Reply