Sandbox firewall now supports request proxying and filtering
Vercel Sandbox firewall now enables forwarding HTTP requests to your own proxy for logging, debugging, or transforming responses. You can use matchers to filter which requests get forwarded based on path, method, query string, or headers, giving fine-grained control over sandbox traffic routing.
The now supports forwarding specific HTTP requests to a proxy you control. You can also use matchers to filter forwarding and credentials brokering to only the requests that need it.Vercel Sandbox firewall
You can now route outbound sandbox traffic through your own proxy for logging, debugging, or transforming requests and responses. Set a on any allowed domain, and the firewall will forward matching HTTPS requests to your server.forwardURL
The proxy receives the original request along with additional headers to identify the source:
Additionally, you can now use matchers to filter request forwarding or to requests matching a specific path, method, query string, or headers. This gives you fine-grained control over which requests get transformed; for example, only forwarding requests to a specific API path while allowing all other traffic through untouched.credentials brokeringPOST
These features are available in beta for Pro and Enterprise plans. Get started by installing the SDK, and learn more in the docs about and .@vercel/sandbox@betarequests proxyingmatchers
Requests proxying
Filtering
: The original request's SNI
vercel-forwarded-host: The original request's scheme
vercel-forwarded-scheme: The original request's port
vercel-forwarded-port: A Vercel-issued OIDC token that the proxy can use to authenticate the request and identity the source team / project / sandbox. Learn more about it in the
vercel-sandbox-oidc-tokendocs
Source: original entry ↗