Testing c/side on staging Environments

Overview

Our customers often like to test out the proxy on a staging environment before taking it to production. While this is fully supported, it's important to note that developer environments differ from production sites in several ways.

Common Considerations

IP Restrictions

• If a staging environment is only accessible to specific IPs, we cannot retrieve the payload of first-party scripts
• Third-party scripts will continue to work as they are typically publicly accessible
• The dashboard will still display the list of scripts but won't show the payload of first-party scripts

SSL Certificates

• First-party scripts require valid SSL certificate validation
• Self-signed certificates will prevent first-party scripts from appearing in the dashboard

Local Testing

• Local testing environments are supported
• Important: For c/side to proxy scripts correctly, the host header must match the site's host header configured in c/side