Can my web app use a UNIX socket on OS X Server? I'd rather have my Mavericks web app use a UNIX domain socket instead of a TCP port to effect a reverse proxy. I've tried using variants of the Apache syntax for UDS in the proxies section of the web app plist but nothing I've tried seems to please OS X Server.

Proxying to gunicorn over TCP port 8001 seems to work in the code below but I'd rather use sockets if I can - keeps my apps separate from OS X Servers' apps.

&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"&gt;
&lt;plist version="1.0"&gt;
&lt;dict&gt;
        &lt;key&gt;name&lt;/key&gt;
        &lt;string&gt;com.iainhouston.django&lt;/string&gt;

        &lt;key&gt;displayName&lt;/key&gt;          &lt;!-- Name shown in Server app --&gt;
        &lt;string&gt;TDD Django test at /django&lt;/string&gt;

        &lt;key&gt;installationIndicatorFilePath&lt;/key&gt;        &lt;!-- The presence of this file indicates web app is installed --&gt;
        &lt;string&gt;/usr/local/python_projects/testwsgi3/hello.py&lt;/string&gt;

        &lt;key&gt;requiredModuleNames&lt;/key&gt;
        &lt;array&gt;
                &lt;string&gt;proxy_module&lt;/string&gt;
        &lt;/array&gt;

        &lt;key&gt;proxies&lt;/key&gt;
        &lt;dict&gt;
                &lt;key&gt;/django&lt;/key&gt;
                &lt;dict&gt;
                        &lt;key&gt;path&lt;/key&gt;
                        &lt;string&gt;/django&lt;/string&gt;
                        &lt;key&gt;urls&lt;/key&gt;
                        &lt;array&gt;
                                &lt;string&gt;http://localhost:8001&lt;/string&gt;
                        &lt;/array&gt;
                &lt;/dict&gt;
        &lt;/dict&gt;
&lt;/dict&gt;
&lt;/plist&gt;


[Update: actual code posted above]

If you've tried this I'd be grateful to know how you got on.
It seems that the answer is No as OS X Server (3.2.1 as of today) comes with Apache 2.2 and from the Apache mod_proxy documents it seems that UDS support wasn't implemented in that release. I was reading a later version's documents.

Not wanting to recompile Apache on our production server, I will have to content myself with TCP ports - no real problem.