You are here:
URL Evaluation and Resolution
When a customer enters a URL into their browser navigation bar, B2C Commerce evaluates the URL and resolves it in this sequence.
This topic assumes that the URL Rules module is enabled. If you’re using the legacy search-friendly URLs module, see URL Evaluation and Resolution for Legacy Search-Friendly URLs
If there are two identical URLs generated by the URL Rules module, B2C Commerce generates a conflict report that can be viewed on the URL Rules Page General tab.
- If the entered URL matches a host name in the host alias file, the B2C Commerce server processes the host name to site mapping.
-
The locale is resolved.
If the URL Rule module is enabled and the locale mapping is set to path, then the first two elements of the URL are used to evaluate the locale. You can create a locale that uses one or two elements in the path. For example:
http://mystore.com/s/SiteGenesis/en/mens http://mystore.com/s/SiteGenesis/de/DE/mensSee also URL Rules Page Settings Tab for information about defining locale mappings.
-
- The URL is processed:
- New URLs are resolved to the correct content asset, product, or other object.
- Pipeline URLs resolve.
- Folder URLs resolve.
- If a URL redirect for the incoming URL is found; it is executed. See also URL Redirects.
- If the URL can't be resolved:
- If a URL doesn't match any object, this can be because of case
differences in the URL or unencoded characters, The URL is resolved using
case insensitive matching and substituting encoded characters for the
following set of unencoded characters:
, @ ) ! $ ' (~ - Try to find the URL in the URL archive and resolve to the corresponding object. First check for a URL redirect from the incoming URL, otherwise redirect to new short URL of the object.
- If a URL doesn't match any object, this can be because of case
differences in the URL or unencoded characters, The URL is resolved using
case insensitive matching and substituting encoded characters for the
following set of unencoded characters:
- If not in the URL archive, check for URL redirects for the incoming URL and execute.
- Otherwise, fall back to Mapping Rules. The URL handling (dynamic/static) hasn’t changed from previous versions.
- New URLs are resolved to the correct content asset, product, or other object.

