If Web Server Rewrites are enabled, inserts the Store Code of the current view in the URL.

Options include: Yes / No

The full address of the Magento root folder that is not running over an encrypted (SSL) channel. The base URL must include a trailing slash.

A markup tag that represents the unsecure base URL.

{{unsecure_base_url}}

A markup tag that points to the folder where the files for the unsecure site’s skin reside. By default, the folder is called “skin.”

{{unsecure_base_url}}skin/

If your Magento installation has multiple sites that use the same folder structure, you can have a different skin folder for each site. Set the configuration scope to the correct site before entering the base skin URL.

You can also specify a skin folder that resides outside of your Magento installation.

A markup tag that points to a folder where the catalog images for this website are located. By default, the folder is called “media.”

{{unsecure_base_url}}media/

If your Magento installation has multiple sites that use the same folder structure, you can have different media folders for each. This gives you the ability to use backup and rollback separately for each media folder.

You can also specify a media folder that resides outside of your Magento installation.

The full address of the Magento root folder that is running over an encrypted (SSL) channel. The base URL must include a trailing slash.

A markup tag that represents the secure base URL.

{{secure_base_url}}

A markup tag that points to the folder where the files for the secure site’s skin reside. By default, the folder is called “skin.”

{{secure_base_url}}skin/

If your Magento installation has multiple sites that use the same folder structure, you can have a different skin folder for each. Set the configuration scope to the correct site before entering the base skin URL.

You can also specify a skin folder that resides outside of your Magento installation.

A markup tag that points to a folder where the catalog images are located. By default, the folder is called “media.”

{{secure_base_url}}media/

If your Magento installation has multiple sites that use the same folder structure, you can have different media folders for each. This gives you the ability to use backup and rollback separately for each media folder.

You can also specify a media folder that resides outside of your Magento installation.

A markup tag that points to the folder where the JavaScript files are located. By default, the folder is called “js.”

{{secure_base_url}}js/

If your Magento installation has multiple sites that use the same folder structure, you can have a different JavaScript folder for each. This gives you the ability to update the scripts separately.

You can also specify a JavaScript folder that resides outside of your Magento installation.

If your domain has a security certificate, you can choose to run the storefront, with or without SSL encryption. Options include:

If your domain has a security certificate, you can choose to run the store Admin, with or without SSL encryption. Options include:

Indicates the landing page that is associated with the base URL. This is set by default to “cms” to indicate a page from Magento’s content management system.

You can also use a different type of landing page, such as a blog. For example, if a blog is installed on the server at magento/blog, you can enter the name of the “blog” folder as a relative path to the selection of pages.

To choose the home page for the store, simply select the CMS page from the list.

By default, the CMS Home Page lists the entire selection of CMS pages that are available for your store.

Contains the URL of the default page that you want to appear when if a 404 “Page not Found” error occurs. The default value is: cms/index/noRoute

Identifies a specific CMS page that you want to appear when a 404 “Page Not Found” error occurs. The default core content page is “404 Not Found.”

Identifies a specific CMS page that appears when cookies are not enabled for the browser. The page explains why cookies are used, and how to enable them for each browser. The default core content page is “Enable Cookies.”

Determines how long a cookie can exist before it is automatically deleted. The default value is set to one hour, in seconds: 3600.

Specifies the folders on the server where Magento cookies can be used. To make Magento cookies available everywhere in the installation, set the Cookie Path to a single forward slash: /

Determines if Magento cookies are available to subdomains. For example, to support the following subdomain:

http://subdomain.domain.com/

Enter the name of your domain with a period at the beginning:

.domain.com

Determines if Magento Cookies can be used only over an unsecure channel (http), or can also be used over an encrypted channel (https). Options include: Yes / No

Verifies that the IP Address of a request matches $_SESSION data. The session terminates if a different IP address is detected. Options include: Yes / No

Verifies incoming proxy data. Checks that the proxy address of a request matches $_SESSION data. The session terminates if a different proxy address is detected. Options include: Yes / No

Verifies outgoing proxy data. Checks that the forwarded-for address of a request matches $_SESSION data. The session terminates if a different forwarded-for address is detected. Options include: Yes / No

USER_AGENT refers to the browser or device that is used to access the website. Verifies that the name and version of the browser, and operating system matches $_SESSION data. The session terminates if a different user agent is detected from one request to another in the same session.Options include: Yes / No

If cookies are disabled by the browser, redirects automatically to the “CMS No Cookies Page.” Options include: Yes / No