HTTP redirect: 301 (permanent) vs. 302 (temporary)

by

Status 301 means that the resource (page) is moved permanently to a new location. The client/browser should not attempt to request the original location but use the new location from now on.

Status 302 means that the resource is temporarily located somewhere else, and the client/browser should continue requesting the original url.

More Related Contents:

  1. What does HTTP/1.1 302 mean exactly?
  2. How long do browsers cache HTTP 301s?
  3. http to https through .htaccess
  4. CORS request with Preflight and redirect: disallowed. Workarounds?
  5. Is a 302 redirect to relative URL valid, or invalid?
  6. How to redirect user’s browser URL to a different page in Nodejs?
  7. What’s the difference between a 302 and a 307 redirect?
  8. Difference between HTTP redirect codes
  9. What’s the difference between HTTP 301 and 308 status codes?
  10. Why can’t I set a cookie and redirect?
  11. URL hash is persisting between redirects
  12. What is correct HTTP status code when redirecting to a login page?
  13. Sending browser cookies during a 302 redirect
  14. Intercepting backend 301/302 redirects (proxy_pass) and rewriting to another location block possible?
  15. luaSocket HTTP requests always respond with a redirect (301 or 302)
  16. htaccess redirect for non-www both http and https
  17. What is the maximum length of a URL in different browsers?
  18. Is there a practical HTTP Header length limit?
  19. Why do I need to use http.StripPrefix to access my static files?
  20. What is httpinterceptor equivalent in angular2?
  21. How to make external HTTP requests with Node.js [closed]
  22. Golang read request body multiple times [duplicate]
  23. What is the difference between HTTP_CLIENT_IP and HTTP_X_FORWARDED_FOR?
  24. Should I URL-encode POST data?
  25. How are cookies passed in the HTTP protocol?
  26. What is the http-header “X-XSS-Protection”?
  27. How to cancel a HTTPRequest in Angular 2?
  28. Correctly switching between HTTP and HTTPS using .htaccess
  29. Console errors. Failed to load resource: net::ERR_INSECURE_RESPONSE
  30. What to do with errors when streaming the body of an Http request

Leave a Comment