Skip to main content

Vercel Sandbox firewall now supports request proxying and filtering

By Steven Van ·

Vercel Sandbox's firewall can now forward matching HTTPS requests to a proxy you run, filtered by path, method, or headers.

Vercel Sandbox's firewall can now forward outbound requests to a proxy you control. Setting a forwardURL on an allowed domain routes matching HTTPS traffic from the sandbox to your own server for logging, debugging, or transforming requests and responses, rather than letting it go straight to the destination.

  • The proxy receives the original request plus headers identifying its source: vercel-forwarded-host (the original SNI), vercel-forwarded-scheme, vercel-forwarded-port, and vercel-sandbox-oidc-token, a Vercel-issued OIDC token the proxy can use to authenticate the request and identify the team, project, and sandbox it came from.
  • New matchers let a rule filter which requests get forwarded or have credentials brokered into them, based on path, method, query string, or headers, so a rule can, for example, forward only POST requests to a specific API path while other traffic to the same domain passes through untouched.

The features are in beta.

Vercel
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →

Read the original announcement →

Read Vercel Sandbox firewall now supports request proxying and filtering on Creators Toolbox