Follow Redirects from Origin

Our edges automatically handle and follow HTTP redirects issued by the origin server.

When the origin server responds with an HTTP redirect status code (e.g., 301 or 302), instead of forwarding the redirect response to the user, we intercept it and automatically initiate a new request to the redirected URL on behalf of the user.

This feature offloads the client from the burden of handling redirects, reducing the need for additional round trips and potential delays, hence improving the overall content delivery experience.