Redirect vs URL rewrite in an API gateway`: The Traffic Policy engine of ngrok allows developers to configure actions that can modify the behavior of traffic flowing through their endpoints. Two common actions are `redirect` and `url-rewrite`, which enable redirection or URL modification before the request reaches the upstream server. While both actions achieve similar goals, such as migrating to a new version of an API, they differ in how they handle client notifications and user experience. Redirects provide more explicit communication with clients through HTTP status codes, whereas URL rewrites offer a seamless user experience by modifying URLs without affecting client requests. The choice between the two actions depends on whether clients need to be notified of changes or not.