I had asked about how one takes a web application from a NCSA httpd
configuration and move it to the web server bundled with Solaris 2.6, SWS.
Most replies suggested I either just move NCSA httpd to the Solaris 2.6 system,
or that I go with Apache, as the configuration files are basically the same. One
person provided enough information that, along with discovering that
documentation is installed as the default page on the newly installed server, I
have been able to hack together a solution.
The only problem I have is controlling access to the cgi interface. I want to
allow access to the cgi interface files, but prevent generating a directory
listing of the cgi directory I am adding (via a pair of map directives in the
/etc/http/httpd.conf file). Otherwise, I think I am getting a hang of the SWS
configuration mechanism and its access control facility. It seems to be built
more for web servers providing multiple virtual host support, but it also its
FAR faster than my old configuration... and its good enough and secure enough to
allow me to deploy it.
My thanks to:
"D. Stewart McLeod" <firstname.lastname@example.org>
Mike Myers <email@example.com>
Jon Mitchell <firstname.lastname@example.org>
email@example.com (Thomas Anders)
James Harmon <firstname.lastname@example.org>
Oh, by the way... it was pointed out that Sun uses Apache and not their own SWS.
Anyone want to explain why they don't use their own product and expect us to?
Marc S. Gibian
COMSYS Information Technology Services phone: (781) 377-6350
PRISM/TFS email: email@example.com
or is it: firstname.lastname@example.org
well, maybe: email@example.com
and if all else fails: firstname.lastname@example.org
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:31 CDT