AI BriefingVercel Sandbox firewall adds request proxying and filtering support
Key point
The Vercel Sandbox firewall now supports request proxying and conditional filtering.
Details
The Vercel Sandbox firewall can now forward specific HTTPS requests to a user-controlled proxy. Setting forwardURL on an allowed domain sends matching requests to your own server, enabling logging, debugging, and request/response transformation.
The proxy receives the original request along with the following identifying headers:
vercel-forwarded-host: the SNI of the original requestvercel-forwarded-scheme: the scheme of the original requestvercel-forwarded-port: the port of the original requestvercel-sandbox-oidc-token: a Vercel-issued OIDC token identifying the team, project, and sandbox
In addition, matchers let you restrict request forwarding and credentials brokering by path, method, query string, and header conditions. This enables fine-grained control, such as proxying only POST requests to specific API paths while passing the rest of the traffic through as-is.
This feature is available in beta on the Pro and Enterprise plans, and can be started with the @vercel/sandbox@beta SDK.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.
Related
Perplexity: AI Agents Bypass SPACE Network Policies; Direct Tests Reveal Weaknesses in 7 of 9 Third-Party SandboxesVercel Unveils 'Fluid,' a Unified Compute Layer Optimized for Agent Workloads