Added note about why Next.js used 307 and 308 status codes#35325
Merged
kodiakhq[bot] merged 3 commits intovercel:canaryfrom Mar 19, 2022
Merged
Added note about why Next.js used 307 and 308 status codes#35325kodiakhq[bot] merged 3 commits intovercel:canaryfrom
kodiakhq[bot] merged 3 commits intovercel:canaryfrom
Conversation
styfle
reviewed
Mar 15, 2022
Co-authored-by: Steven <steven@ceriously.com>
ijjk
approved these changes
Mar 19, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
fixes #numbercontributing.mdFeature
fixes #numbercontributing.mdDocumentation / Examples
yarn lint