Caveats

c/side is currently in a beta phase. We are actively working on improving every aspect of our product daily. With a beta product, there are some caveats to be aware of.

c/side's Web Script

c/side's web script has a few caveats that the end user should be aware of while implementing it.

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.

Staging Environments / Environments That Use a Different Domain

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.

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.

We plan to add support for this before we release out of beta. An easy workaround for this is to conditionally render the c/side web script based on your environment.

Whitelisted Scripts

c/side has a small list of scripts that will bypass our proxying. Here is a list of scripts that we currently whitelist:

We plan to allow end users to add their own whitelist of scripts in the future. But for now, this list is static and is only modified by c/side.