Caveats

Environments That Use a Different Domain

Staging environment

In order for c/side to accurately and safely license our proxy, we use the referrer header in the requests to determine if the request is coming from a licensed customer. This approach may come with some caveats.

For example, if you use a staging environment, c/side will not be able to accurately license the proxy for the scripts. This is because the referrer header will (often) be a different domain. This is often seen for preview/staging URLs that use a dynamically generated domain, like Vercel, Netlify, and other platforms.

Local environment

We have added some detection mechanisms to the web script to help with local environments, such as localhost, 127.0.0.1, ::1 and other cases to automatically disable the web script from proxying in those environments. If you do not want your proxy to run in the local environement, you can conditionally render the c/side web script.

Inline Scripts

c/side currently does not monitor inline scripts. We plan to add support for monitoring inline scripts in the future. We recommend that you use the src attribute to load your scripts, instead of using inline. But we understand that this may not always be possible.

Server side prefixing

For optimal performance & protection, you must also prefix any URLs used in <script> tags within the HTML sent to the browser. The reason why is explained in the Server side prefixing section.

Bypassed domains

Some third party scripts are known to cause conflicts when being served from another domain. We maintain a list of these domains here.