Oracle B12255-01 - Manual (Page 166)

9-2 Oracle HTTP Server Administrator’s Guide
Creating Application-specific Error Pages
Oracle HTTP Server has a default content handler for dealing with errors. You can
use the ErrorDocument directive to override the defaults.
Offering HTTPS to ISP (Virtual Host) Customers
For HTTP, Oracle HTTP Server supports two types of virtual hosts: name-based and
IP-based. HTTPS supports only IP-based virtual hosts.
If you are using IP-based virtual hosts for HTTP, then the customer has a virtual
server listening on port 80 of a per-customer IP address. To provide HTTPS for
these customers, simply add an additional virtual host for each user listening on
port 4443 of that same per-customer IP address and use SSL directives, such as
SSLRequireSSL to specify the per-customer SSL characteristics. Note that each
customer can have their own wallet and server certificate.
If you are using name-based virtual hosts for HTTP, each customer has a virtual
server listening on port 80 of a shared IP address. To provide HTTPS for those
customers, you can add a single shared IP virtual host listening on port 4443 of the
shared IP address. All customers will share the SSL configuration, including the
wallet and ISP’s server certificate.
Using Oracle HTTP Server as Cache
You can use the Oracle HTTP Server as a cache by setting the ProxyRequests to
“On” and CacheRoot directives.
See Also: “ErrorDocument directive” in the Apache Server
documentation.
See Also: "Running Oracle HTTP Server as Root" on page 4-2 for
instructions on running Oracle HTTP Server with ports lesser than
1024.
See Also: “ProxyRequests and CacheRoot directives” in the
Apache Server documentation.