vtex-io-service-paths-and-cdn

To configure edge caching for VTEX IO service routes, you define path prefixes and Cache-Control headers in your service.json file to match data sensitivity and determine CDN behavior. This aligns route classification with edge caching rules for Node or .NET backends, ensuring correct interaction.

Public, segment, and private path prefixes in VTEX IO classify routes by data sensitivity and cookie visibility. Public prefixes allow broad edge caching, segment targets specific user data, and private restricts caching while exposing necessary cookies to the client browser.

You align Cache-Control headers with data scope by selecting the correct path prefix in service.json. This configuration ensures that public, segment, or private endpoints across Node or .NET IO backends enforce the appropriate CDN caching constraints.

Yes, service.json configurations control cookie visibility by mapping routes to public, segment, or private path prefixes. This route classification determines which cookies are exposed to the client and how data is managed at the CDN edge.

VTEX IO CDN edge caching fails for private routes when path prefixes and Cache-Control headers are misaligned in service.json. Troubleshooting route prefix classification ensures that sensitive data is not cached at the edge and cookies remain correctly managed.

Yes, you must classify all routes in service.json for Node and .NET IO backends. Applying public, segment, or private path prefixes is required to determine cookie visibility and enforce correct edge caching behavior for every endpoint.