HTTP 302 Found

Redirection code, RFC 9110, section 15.4.3

What it means

The page is somewhere else for now, but keep using the original address in the future.

A real response

This is the request and the answer our test server gave when we asked it to return 302.

GET /c/302 HTTP/1.1
Host: example.com

HTTP/1.1 302 Found
Date: Sat, 14 Nov 2026 10:00:00 GMT
Content-Type: text/html; charset=utf-8
Location: /new-page
Content-Length: 11

<p>demo</p>

What browsers do with a POST

We sent a POST with the body hello to a test server that answered 302 and then reported what arrived at the new address. Chrome 157 sent GET and dropped the body. WebKit sent GET and dropped the body.

If you run the site

Use 302 for a temporary move, such as a short maintenance page or a login redirect. Like 301, many browsers change POST to GET. If you want the method kept, send 307. If you move a page for good, use 301 or 308, not 302, so that search engines move the address too.

If you are a visitor

Your browser follows it by itself.

A common mistake

Using 302 for a permanent move and then wondering why search results still show the old address.

Registered in the IANA HTTP Status Code Registry as Found, defined in RFC 9110, section 15.4.3.

This is an independent guide. It is not connected with the IETF, IANA, any browser maker or any company named here. Meanings were checked against the RFC texts on 14 November 2026. Responses shown were recorded on 14 November 2026 from a small test server on the author's own computer.