Skip to content

docs: change _rewrites to _redirects in docs #1895

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 19, 2023
Merged

docs: change _rewrites to _redirects in docs #1895

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/redirects-rewrites.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,9 @@ so there are some considerations in deciding which one to use with your site.
only applies to rewrites, not redirects.
- If you need Next.js-specific features such as regex path or header matching, you must use Next.js rewrites.

### Using `_rewrites` and `_headers` files
### Using `_redirects` and `_headers` files

If you are using `_rewrites` or `_headers` files rather than a `netlify.toml` file, bear in mind that these files must
If you are using `_redirects` or `_headers` files rather than a `netlify.toml` file, bear in mind that these files must
be in the published directory of your site, not the root of the repo. To do this, put them in `public` and they will be
moved into `.next` at build time. Do not put them directly into `.next`, because it is emptied at build time. Any
`_rewrites` or `_headers` files in the root of the repo will not be found when deployed.
`_redirects` or `_headers` files in the root of the repo will not be found when deployed.