Currently Being ModeratedApr 11, 2013 7:19 AM (in response to params)
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.
Currently Being ModeratedApr 11, 2013 9:01 AM (in response to MrHoffman)
Hi. Yes, it is a continuation of my last post but the web application is working currently with the manual edit of the config file which, unfortunately, causes the Web function of Server Admin to not function properly for some apparent reason.
The funny and sad part is when I asked me about any documentation pertaining to this application, they stated they didn’t write any while they were creating the application. ** On a side-note, I came into this project more than 90% of its completion **. So it has been rather cumbersome trying to get much information out of them.
We are currently running 10.6 … We could move to the newer server version but that would entail us starting from scratch with all that is setup on the mac server currently.
Currently Being ModeratedApr 11, 2013 1:04 PM (in response to params)
These sorts of problems, and no documentation? Escalate this situation to your management, and allow them to sort this out.
There's either an error in the previous edit, or the edit is incompatible with Server Admin. Check the system logs for details. With Apache, there's also a command-line configuration test mechanism which can detect various errors. The following is an example of the command:
$ apachectl configtest