|
|
|
HP WebWise MPE/iX Secure Web Server installs in a different
HFS directory tree than Apache, and so will
not overlay your existing Apache environment in any way. If you
want to run both HP WebWise MPE/iX Secure Web Server and Apache
at the same time on the same machine, make sure you configure HP
WebWise MPE/iX Secure Web Server to use different TCP listening
ports than Apache.
HP WebWise MPE/iX Secure Web Server is based on Apache 1.3.9,
whereas Apache for MPE/iX 6.0 and 6.5 is based on Apache 1.3.4.
All Apache functionality should be compatible with HP WebWise MPE/iX
Secure Web Server, but there may be some non-SSL, non-X.509 functionality
in HP WebWise MPE/iX Secure Web Server that is not backward compatible
with Apache for MPE/iX.
The HP WebWise MPE/iX Secure Web Server JHTTPDS job specifies
a umask of 007 so that log files are created with secure file permissions,
whereas the Apache JHTTPD job uses a default umask of 000. Apache
CGI applications which rely on the default umask of 000 for creating
world-readable files may have trouble on HP WebWise MPE/iX Secure Web
Server because the new umask of 007 forbids any kind of world access.
Instead of relying on a customer-changeable attribute like the umask,
these CGI applications should be rewritten to explicitly specify
the desired umask and file permissions at file creation time. If
specifying umask and permissions at creation time isn't
a viable option, an alternative would be to use chmod after the
file has been created, but this leaves a small window between creation
and chmod where the permissions will be determined by the JHTTPDS umask.
|
Complete PDF