URL Routing in Commerce Websites
Understanding how URL routing works within the context of your Commerce website enables you to effectively implement redirects. The way in which a URL is requested determines the layers of processing that take place before the final page is displayed to users. The following image illustrates the basic ways URL routing can occur:
As you review the preceding flow chart, note these URL routing sequences:
-
The difference between a URL requested by a user through the browser address bar as opposed to one requested internally within a Backbone single-page application (SPA).
-
How URL redirects in the NetSuite application are handled.
-
How redirecting a user in a SuiteScript Server Page (SSP) is handled after an SSP has started loading.
-
How URLs within an SPA are routed.
An additional scenario not illustrated in the flow chart is the routing that occurs for URLs that originate from within an SPA, but trigger behavior similar to a user entering a URL directly into an address bar. For SuiteCommerce websites, this occurs when a user is directed to an SSP outside of the current SSP. For example, this can happen when a user is using the touch point for shopping (shopping.ssp) and then proceeds to the checkout (checkout.ssp) or their account (myaccount.ssp).
Read the following sections to learn more about URL routing in Commerce websites and the best ways to redirect users in particular scenarios.