Fixed blog.html redirect #10771
Merged
Fixed blog.html redirect #10771
Conversation
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
bvaughn
force-pushed
the
gatsby-better-redirect-support
branch
from
7ac3f17 to
73e84fa
Compare
|
Deploy preview ready! Built with commit b463ff1 |
This was referenced May 20, 2020
This was referenced Mar 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Corresponds to gatsbyjs/gatsby/pull/2185
In development, Gatsby honors these redirects by just loading the
toPathpage. In production, the newgatsby-plugin-netlifyplugin writes a_redirectsfile that looks like this:Based on these Netlify docs and this online validator I expect that to work.