Reroute requests to a CMS backend
Reroute incoming requests from an ÃÛ¶¹ÊÓƵ Commerce store to a separate WordPress site using the Fastly Edge Module Other CMS/backend integration with an Edge Dictionary. You can follow a similar process to reroute requests to other CMS backends.
Use Fastly Edge Modules to create and upload custom VCL code from the Admin instead of manually writing the VCL code and uploading it using the Fastly API.
Prerequisites
-
Your environment must be configured to use the Fastly CDN. See Configure Fastly services.
-
Ensure that you are running the latest version of the Fastly CDN module for Magento 2. See Upgrade the Fastly Module.
-
Verify the environment configuration for the Fastly service. See Check Fastly caching.
-
You must have Admin credentials to access the Staging and Production environments.
To reroute requests from ÃÛ¶¹ÊÓƵ Commerce to WordPress:
-
Enable Fastly Edge Modules in the Staging or Production environment.
-
Log in to the Admin.
-
Navigate to Stores > Settings > Configuration > Advanced > System > Full Page Cache > Fastly Configuration > Advanced Configuration.
-
Set the value for Fastly Edge Modules to Yes.
-
Save the configuration.
-
-
Identify the URL paths to reroute to the WordPress backend.
-
Complete the following tasks to configure the Fastly service and create the custom VCL code for rerouting requests to the WordPress backend.
-
Create an Edge Dictionary that specifies the paths to reroute from the ÃÛ¶¹ÊÓƵ Commerce store to the backend.
-
Add the WordPress backend to the Fastly service configuration and attach the request condition for the URL rewrites.
-
Configure the Other CMS/backend integration Edge Module to handle the URL rewrites from ÃÛ¶¹ÊÓƵ Commerce to the WordPress backend.
For detailed instructions, see in the Fastly CDN module for Magento 2 documentation.
-
-
After updating the Fastly service configuration, test your ÃÛ¶¹ÊÓƵ Commerce store to ensure that the specified URL requests for WordPress are rerouted correctly.