In my _redirects, I have specified: /api/* /.netlify/functions/:splat 200! I tried with/out the bang (!) In development ,using netlify cli, the redirect works just fine. http://localhost:8888/api/latestTracks In production, https://website.netlify.app/api/latestTracks leads to a 404. Otherwise o…

Hey @djmtype Can you share your _redirects file? Where is the _redirects file placed in the repository? Does the deploy log show your redirects are processed e.g. [redirects-processed]

No redirects were processed. Is there a Gridsome-specific thing why it ignored my _redirects file? _redirects file: /api/* /.netlify/functions/:splat 200 /api/* https://gridsome-spotify-matrix.netlify.app/api/:splat 200 I added the 2nd line after to see if that would solve it. Nope.

[image] djmtype: Is there a Gridsome-specific thing why it ignored my _redirects file? Where have you placed the _redirects file? Is it in the static directory?

It also looks like a Gridsome directory thing as returned from Netlify Deploy. A “_redirects” file is present in the repository but is missing in the publish directory “dist”. Fair enough. I wrote it to the netlify.toml file instead: [[redirects]] from = "/api/*" to = "/.netlify/functions/:…

I had originally placed the _redirects file on the same level as the functions directory and netlify.toml – at the root. Then I had tried placing it in the src directory, hoping when Netlify built the project, it would copy it over to dist. However, that didn’t work, and threw an error on the public…

Thanks, and yes that does work too.

I found a downside to placing _redirects inside static directory. When running netlify cli in development, _redirects can’t be found because it might be looking for it in the root? http://localhost:8888/api/latestTracks results in a 404, but http://localhost:8888/.netlify/functions/latestTracks wo…

When using Gridsome, setting up redirects in netlify.toml seems like the easier option that works in both development and production. [[redirects]] from = "/api/*" to = "/.netlify/functions/:splat" status = 200 However, you might want a different redirects in production than in development.

Gridsome only copies static to dist during build, and seems to ignore when running in dev mode. Thus is appears using a netlify.toml a better option. [image] djmtype: However, you might want a different redirects in production than in development. You can use both _redirects and [redirects] …

Netlify redirects not working in production

Support

coelmay February 19, 2022, 9:09pm 7

As per Gridsome documentation

Files in this directory will be copied directly to dist during build

So in order for the _redirects file to get copied to dist for Netlify to process, you need to place it in the static directory in the project.

Page not found on a specific page

Topic		Replies	Views
Redirect rules for Gridsome site processed during build, but not redirecting Support redirects	1	948	May 5, 2020
Redirects not being processed in production, works fine locally Support redirects	13	2451	May 24, 2021
Copy custom _redirects file to /dist Support netlify-newbie , redirects	1	502	August 31, 2020
30 redirects not working Support redirects	12	618	February 3, 2022
Correct file location for redirects file - redirects not working as expected Support redirects	13	6013	December 4, 2019

Netlify redirects not working in production

Related topics