Added note about why Next.js used 307 and 308 status codes #35325

molebox · 2022-03-15T08:24:11Z

This PR looks to clear up some confusion users are having around our decision to use 307 and 308 redirects, instead of 301 and 302

Bug

Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
Related issues linked using fixes #number
Integration tests added
Documentation added
Telemetry added. In case of a feature if it's used or not.
Errors have helpful link attached, see contributing.md

docs/api-reference/next.config.js/redirects.md

Co-authored-by: Steven <steven@ceriously.com>

Added note about why Next.js used 307 and 308 status codes

d0f2976

molebox requested review from timneutkens, ijjk, shuding, styfle, huozhi, padmaia and leerob as code owners March 15, 2022 08:24

ijjk added area: documentation labels Mar 15, 2022

styfle reviewed Mar 15, 2022

View reviewed changes

docs/api-reference/next.config.js/redirects.md Outdated Show resolved Hide resolved

Apply suggestions from code review

8901cba

Co-authored-by: Steven <steven@ceriously.com>

ijjk approved these changes Mar 19, 2022

View reviewed changes

Merge branch 'canary' into additional-redirect-note

baf34f5

kodiakhq bot merged commit 6f24c20 into vercel:canary Mar 19, 2022

github-actions bot locked as resolved and limited conversation to collaborators Apr 19, 2022