vtex-io-service-paths-and-cdn

To stop CloudFront from caching personalized VTEX IO responses, align your Cache-Control headers with data sensitivity and use private path prefixes like `/_v/private/...` for authenticated shopper data.

The correct service.json route path prefix for segment-scoped data in VTEX IO is `/_v/segment/...`, which ensures the `vtex_segment` and `vtex_session` cookies are available to your service.

The vtex_segment cookies are missing because your service.json route uses a public path prefix instead of a segment or private prefix, preventing the edge from forwarding the required cookies.

Configure Cache-Control headers for VTEX IO endpoints by setting cacheable policies for anonymous public paths and restricting cacheability via private prefixes for authenticated endpoints to prevent edge leaks.

You cannot use a public path prefix for VTEX IO routes returning shopper order history because public paths restrict cookie visibility, preventing the service from accessing the required authentication context.

The best way to troubleshoot unexpected edge caching behavior in VTEX IO is to verify that your service.json path prefix matches the required cookie visibility and that Cache-Control aligns with data sensitivity.