How to setup Web Proxy within Server Admin utility?

Question

Hi. We currenlty use the Web function within the Server Admin utility for all our web hosting applications running on Snow Leopard server. Recently we had a vendor create a website application which needs a proxy setup in order work. According to them, we need a proxy to 127.0.0.1:8000 for the site. At the moment, they manually edited the .config file for the website to edit the proxy settings which consequently caused the Web function within Server Admin to stop functioning properly as I found a website stating that if a config file is manually edited outside of the Server Admin, the Web function will not function properly. The error message I got was "Uncaught exception raised in Web client-side plugin".
The .config file which was manually edited is as such:
<VirtualHost **.**.**.***:**>
    ServerAdmin [email protected]
    ServerName demo.segmentthis.com
    ServerAlias demo.segmentthis.com
    ProxyRequests off
    <Proxy *>
Order deny,allow
Allow from all
    </Proxy>
    <Location />
ProxyPass http://localhost:8000/
ProxyPassReverse http://localhost:8000/
    </Location>
</VirtualHost>
I supposed my question is, is there a way to edit the proxy within the Web function of Server Admin instead of manually editing the config file?
I hope that made some sense but if not, please let me know and I will try to elaborate a bit more.
Thank you very much for your help!

Answer 1

Your question here appears related to or a continuation of this previous question — is this the case?
Based on the previous posting, whatever information you're receiving from the vendor support folks appears rather garbled or confused, particularly based on that "The vendor mentioned that we need to route the DNS and get it working (forwarded) on port 80 and I'd tend to avoid them." comment over there.
I'd ask the vendor for documentation and details (as on its face, a requirement for this proxy seems, well, somewhat questionable), but yes, you're probably in the Apache config files here, and probably using overrides and .htaccess if the site is low-volume, as that'll keep the changes isolated for testing.
Out of curiousity, is this proxy project part of an attempt to get this package to accessible, but without the vendor actually having the package running on port 80?  (Got a pointer to the package?  We can check the docs, and see if we can translate the installation requirements into something useful on OS X Server.)
Are you running 10.5 or 10.6?  Both are pretty old releases.