Getting Started with Oracle HTTP Server 4-9
■
Section 4.4.7, Disabling the Options Method
4.4.1 Configuring Secure Sockets Layer
Secure Sockets Layer SSL is an encrypted communication protocol that is designed to securely send messages across the Internet. It resides between Oracle HTTP Server on
the application layer and the TCPIP layer, transparently handling encryption and decryption when a secure connection is made by a client.
One common use of SSL is to secure Web HTTP communication between a browser and a Web server. This case does not preclude the use of non-secured HTTP. The
secure version is simply HTTP over SSL HTTPS. The differences are that HTTPS uses the URL scheme https: rather than http:.
By default, an SSL listen port is configured and enabled using a default wallet
during Oracle HTTP Server installation. Wallets store your credentials, such as certificate
requests, certificates, and private keys. The default wallet that is automatically installed with Oracle HTTP Server is for
testing purposes only. A real wallet must be created for your production server. The default wallet is located in the ORACLE_INSTANCEconfigOHSohs_
namekeystoresdefault directory. You can either place the new wallet in this location, or change the SSLWallet directive in ORACLE_
INSTANCE
configOHSohs_namessl.conf to point to the location of your real wallet.
4.4.1.1 Using Fusion Middleware Control to Configure a Wallet and SSL
For instructions on configuring wallets and SSL using Fusion Middleware Control, see Enabling SSL for Oracle HTTP Server Virtual Hosts in the Oracle Fusion Middleware
Administrators Guide.
4.4.2 Configuring MIME Settings
Multipurpose Internet Mail Extension MIME settings are used by Oracle HTTP Server to interpret file types, encodings, and languages. MIME settings for Oracle
HTTP Server can only be set using Fusion Middleware Control. You cannot specify the MIME settings using opmnctl commands.
The following tasks can be completed on the MIME Configuration page:
■
Configuring MIME Types
■
Configuring MIME Encoding
■
Configuring MIME Languages
4.4.2.1 Configuring MIME Types
MIME type maps a given file extension to a specified content type. The MIME type is used for filenames containing an extension.
4.4.2.1.1 Using Fusion Middleware Control to Configure MIME Types To configure a MIME
type using Fusion Middleware Control, do the following:
1. Select Administration from the Oracle HTTP Server menu.
2. Select MIME Configuration from the Administration menu. The MIME
configuration page appears.
4-10 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server
3. Click Add Row in MIME Configuration region. A new, blank row is added to the
list.
4.
Enter the MIME type.
5.
Enter the file extension.
6. Review the settings. If the settings are correct, click Apply to apply the changes. If
the settings are incorrect, or you decide to not apply the changes, click Revert to return to the original settings.
7.
Restart Oracle HTTP Server. See Section 4.1.4
. The MIME configuration is saved, and shown on the MIME Configuration page.
4.4.2.2 Configuring MIME Encoding
MIME encoding enables Oracle HTTP Server to determine the file type based on the file extension. You can add and remove MIME encodings. The encoding directive
maps the file extension to a specified encoding type.
1. Select Administration from the Oracle HTTP Server menu.
2. Select MIME Configuration from the Administration menu. The MIME
configuration page appears.
3. Expand the MIME Encoding region by clicking the plus sign + next to MIME
Encoding.
4. Click Add Row in MIME Encoding region. A new, blank row is added to the list.
5. Enter the MIME encoding, such as x-gzip.
6. Enter the file extension, such as .gx.
7. Review the settings. If the settings are correct, click Apply to apply the changes. If
the settings are incorrect, or you decide to not apply the changes, click Revert to return to the original settings.
8. Restart Oracle HTTP Server. See
Section 4.1.4 .
4.4.2.3 Configuring MIME Languages
The MIME language setting maps file extensions to a particular language. This directive is commonly used for content negotiation, in which Oracle HTTP Server
returns the document that most closely matched the preferences set by the client.
1. Select Administration from the Oracle HTTP Server menu.
2. Select MIME Configuration from the Administration menu. The MIME
configuration page appears.
3.
Expand the MIME Languages region by clicking the plus sign + next to MIME Languages.
4. Click Add Row in MIME Languages region. A new, blank row is added to the list.
5.
Enter the MIME language, such as en-US.
6.
Enter the file extension, such as en-us.
7. Review the settings. If the settings are correct, click Apply to apply the changes. If
the settings are incorrect, or you decide to not apply the changes, click Revert to return to the original settings.
8.
Restart Oracle HTTP Server. See Section 4.1.4
.