PriorNotify module used for routing all frontend requests through UPWARD-PHP.

Installs: 8

Dependents: 0

Suggesters: 0

Security: 0

Stars: 0

Watchers: 1

Forks: 0

Open Issues: 0


1.4 2021-07-27 16:25 UTC

This package is auto-updated.

Last update: 2023-03-29 01:06:41 UTC


The Magento 2 UPWARD connector is a module for routing requests to UPWARD-PHP. This module replaces the default Magento frontend theme with a PWA Studio storefront application.

PWA Studio storefront deployments in the Magento Commerce Cloud use this module to keep Magento and storefront code on the same server.


The Magento 2 UPWARD connector module is part of the Magento Cloud deployment steps in the official PWA Studio docs.


The Magento 2 UPWARD connector has additional settings that can be configured in the admin area under:

Stores > Configuration > General > Web > UPWARD PWA Configuration.

General configuration

These are the configurations for the UPWARD process itself.

UPWARD Config File

This configuration is the location of the UPWARD configuration file for the UPWARD-PHP server. It is recommended you follow system-specific best practices and set this value with an environment variable or the magento config:set CLI command.

You may use a path relative to your web root or an absolute path for the value of this configuration.

Relative: fastcgi_param CONFIG__DEFAULT__WEB__UPWARD__PATH pwa/upward.yml Absolute: magento config:set -e web/upward/path /app/node_modules/@magento/venia-concept/dist/upward.yml

Front Name Allowlist

This configuration allows you to specify a line-separated list of routes to forward to the default Magento theme.



With this example, when a visitor navigates to either <Magento store URL>/contact or <Magento store URL>/privacy-policy-cookie-restriction-mode, they will land on a page rendered by Magento instead of the storefront application. Configuration support in the upward-connector module allows your site to send prerendered static html to search bots.

A middleware layer checks each request to see if it comes from a crawler and if allowed, sends it to the prerender service. These configuration entries let you configure which pages to send to to serve the static HTML versions of that page. If a page is not configured for prerendering, the request continues using the normal server routes.

Configuration Description Example
Enable Prerender For Search Bots This enables prerender functionality for this store view.
Prerender URL Url of the prerender service. Token Token to use for the hosted service
Crawler User Agents Line break separated list of keywords to detect the crawler in the user-agent request header
Blocked List Resources that will not be sent for prerendering. Use * as a wildcard character. .js */cart
Allowed List Explicitly allowed resources to be sent for prerendering. If empty, all resources are allowed.

Testing prerendered pages

To see how a crawler sees a prerendered page, set your browser's User Agent to Googlebot and visit your URL. You can also run this on the command line and change the sample URL to your storefront's URL:

curl -A Googlebot > page.html

To configure prerender locally for testing purposes, see

Troubleshooting partial rendered pages

There is no way to tell when a PWA page fully loads. For prerendering it is possible to force prerender to wait for a predefined timeout before setting the window.prerenderReady flag.

Add the following to the runtime script:

window.prerenderReady = false;
setTimeout(function () {
  window.prerenderReady = true;
}, 1000 * 15);

For more information, see

Service Worker Note

Avoid sharing the same hostname between your PWA Studio storefront and the Magento 2 admin backend. This causes the storefront Service Worker to intercept backend requests when you have both the storefront and admin tabs open at the same time on your browser. If you cannot avoid sharing the hostname, access one service at a time or use a private browsing session per service.