You use these settings to define and configure an Upload Directory for use with NetStorage.
An upload directory is a root directory in a storage group, represented by a CP code that has been provisioned for use with NetStorage. You later associate this upload directory with an upload account, to grant it access to this storage group.
Several settings can be applied and are broken down into various categories:
The settings here are used to select the CP code to serve as the upload directory. (Here, you set up a "CP code root" for the storage group).
- Click + Upload Directory to add a new upload directory.
- Do you have a CP code provisioned and
available for use?
- Yes: Select the applicable one. (If you have only one, it is default selected.)
- No: You're given an option to add a new one. A CP code name can be up to 128 alphanumeric characters, but cannot include _ , # ' " % or non-printable characters. It can take up to two hours for a new CP code to provision.
- Additional settings are revealed that allow you to configure the upload directory. They are discussed in the sections that follow.
Security and Advanced Settings
These settings allow you to determine how various requests will be handled by the storage group.
|Download Security||These options are used to determine the level of security that should be
applied to incoming download requests.
As download requests come for content from your selected upload directory via Edge Servers, you can define the level of security that must be met to obtain access:
|SSL Replication||Content in all of your storage groups is replicated to other persistent systems
within the NetStorage network to ensure accessibility (via Geo Replication settings
applied in the storage group).
When this option is set to “ON”, contents within the selected upload directory will be replicated securely via Secure Sockets Layer (SSL).
Note: While this offers added protection for your content, it can take slightly longer for the replication to process.
|Force Case||Based on your environment, you may have specific file-naming
conventions pertaining to the use of upper vs. lowercase text. Additionally, some
web services require that filenames also adhere to a specific case usage model. For
example, a web-based database application may require that all file names be
lowercase, but your environment requires the use of capital letters. The Force Case
functionality can be incorporated in these cases, to change case-usage of your files
Note: NetStorage doesn't automatically apply the Force Case setting to Index requests. If using the Force Case option, you must manually name your index.htm file accordingly. For example, if the Force case setting is set to Convert all requests to uppercase, then you would change the Index Name to INDEX.HTM instead of index.htm.
CAUTION: Before modifying case settings, ensure any files that currently exist in the targeted storage group conform with the selected setting. For example, if Convert all requests to lowercase is selected, all existing files in the storage group must currently be all lowercase. If an option is selected, but existing files do not conform to the selected case setting, a denial of service will result for your end users.
|Path Name Mode||NetStorage doesn't adhere to a traditional directory-based file
system. As a result, characters such as “/” can be used within a directory name. For
example, you could actually name a directory “
|Send Content MD5 Header||
|Query String Mode||If a request targeting the upload directory has a query string value appended
to it, determine how the string should be handled. (This applies to both upload and
download operations targeting the upload directory.)
|Quick Delete||Set this switch to "On" to enable use of the "quick-delete" operation available in the
NetStorage Usage API and the CMShell. This allows you to target a specific directory
in this storage group and recursively delete all of its content. Specific usage
requirements and caveats apply.
Note: Enabling this option changes the default CMShell behavior of the "
|Encoding, Key Order and Exclude||These options allow you to select and enforce the type of encoding to be used
when displaying paths in XML-aware contexts. For example, this applies to call
response output for the “
Enforce Encoding: When set to On, upload operations will verify that all path values defined within the URL for target content are properly formatted using the selected Encoding method. If the path is not properly formatted to meet the selected method, an error will be returned.
Note: This only applies to the use of UTF-8 as an encoding method. If you have selected iso-8859-1, the Enforce Encoding slider is grayed-out and unavailable.
|Serve from Zip||
|Index Name, Limit and Search on 404||
These options, as well as the related, Search on 404 option account for the unique file system supported by NetStorage. They are used to define an "Index File" that should be accessed for requests that do not end in a specific file name and extension. (For example, a request for an object that ends in a trailing slash -- "/".) The "Index File" is similar in functionality to that of Apaches "directory index" auto-index feature. Use these fields as follows: