Vercel Sandbox firewall now supports request proxying and filtering
Vercel Sandbox firewall adds request proxying and path-based matchers in beta, letting Pro and Enterprise users route outbound sandbox traffic through a custom proxy for logging, debugging, or transformation.
The now supports forwarding specific HTTP requests to a proxy you control. You can also use matchers to scope 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 forwardURL on any allowed domain, and the firewall will forward matching HTTPS requests to your server. The proxy receives the original request along with additional headers to identify the source: Additionally, you can now use matchers to limit 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 Those feature 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 Read more Requests proxying Matchers : The original request's SNIvercel-forwarded-host : The original request's…