Module warp::redirect

Redirect requests to a new location.

The types in this module are helpers that implement Reply, and easy to use in order to setup redirects.

Traits

• AsLocation
  Trait for redirect locations. Currently only a Uri can be used in redirect. This sealed trait exists to allow adding possibly new impls so other arguments could be accepted, like maybe just warp::redirect("/v2").

Functions

• found
  HTTP 302 Found (or Temporary Redirect) Description: The requested resource can be found at a different URL temporarily. Usage: Historically, this status code was used for temporary redirects. However, its meaning was often misunderstood, and different clients treated it differently. As a result, it is recommended to use 307 (or 303) for temporary redirects instead. Common Use Case: Rarely used directly due to ambiguity; replaced by 307 or 303.
• permanent
  HTTP 308 Permanent Redirect Description: The requested resource has been permanently moved to a new URL, and future requests should use the new URL. Usage: Similar to 301, but like 307, it preserves the original request method when redirecting. It indicates that the redirection is permanent, and browsers and clients will cache this redirect like they do for 301.
• redirect
  HTTP 301 Moved Permanently Description: The requested resource has been permanently moved to a new URL. Usage: It is used when a URL has permanently moved to a new location. Search engines will update their index to the new URL. Browsers and clients will automatically cache this redirect, so subsequent requests for the old URL will automatically go to the new URL without making a request to the old URL. Common Use Case: Changing domain names, restructuring website URLs.
• see_other
  HTTP 303 See Other Description: The response to the request can be found at a different URL, and the client should retrieve it using the GET method. Usage: It is typically used to redirect the client to another URL using a GET request after processing a POST request. It ensures that the client doesn’t repeat the POST request if they refresh the page. Common Use Case: After form submissions or any non-idempotent request.
• temporary
  HTTP 307 Temporary Redirect: Description: The requested resource can be found at a different URL temporarily. Usage: Similar to 302, but explicitly defined as a temporary redirect. The main difference between 307 and 302 is that 307 preserves the method of the original request when redirecting. If the original request was a POST, the subsequent request to the new URL will also be a POST. Common Use Case: Temporary redirects that should preserve the original request method.