301 Redirect

Hello 😃

I am trying to apply 301 redirect with my Gatsby and S3 + Cloudfront , and so far i have no success , i have about 204 redirect url , i will list below my configuration .

fromPath: `/old-url`,
toPath: `/new-url`,
isPermanent: true,
redirectInBrowser: true,
});
`


 {
      resolve: 'gatsby-plugin-s3',
      options: {
        bucketName: process.env.S3_BUCKET,
        region: 'eu-west-1',
        protocol: 'https',
        hostname: 'stage-mydomain.de',
        bucketPrefix: 'de',
        generateRoutingRules: true,
        generateRedirectObjectsForPermanentRedirects: true,
      }
    }

note that i have no plugin related to redirect inside my config , 
what i would like to accomplish is pure 301 server side redirect , i dont want JS redirect and Meta redirect because 
Js will not work with JS disabled and Meta is not good for SEO . 

can someone help please? 
Thanks

> 

[JoshuaWalsh]

Creating a fork duplicates the project into a repository that you own. You can change that freely. If we make updates to our version you can pull those into your repository, and if you make changes that you think we’d like you can submit a Pull Request to us.

In your website’s package.json you have a line that looks something like this:

"gatsby-plugin-s3": "^0.3.8"

If your fork is hosted on GitHub, you can alter this to point to your fork by doing something like:

"gatsby-plugin-s3": "ahmadkhalaf1/gatsby-plugin-s3"

You can find more details here:

• https://docs.github.com/en/free-pro-team@latest/github/getting-started-with-github/fork-a-repo
• https://docs.npmjs.com/cli/v6/configuring-npm/package-json#git-urls-as-dependencies

Best of luck 😃

[JoshuaWalsh]

302 redirects in S3 Static Website Hosting are usually to add a trailing slash. If you add a trailing slash to your redirect’s toPath it should only need a single 301 redirect.

Thanks for the offer to buy me a beer. We don’t have any mechanism set up for tipping, and I’m just happy that it’s working for you.

Fixing the bug permanently should be fairly straightforward, but first I want guidance from the Gatsby Core team on how they think redirects should be handled. Unfortunately they recently restructured their community, and now it’s harder to get in touch with them. I might try resubmitting my question as a bug instead of a discussion to see if that gets better visibility.

At the moment I’m thinking the best solution would be for us to subtract pathPrefix from the beginning of the fromPath of all redirects, then to add bucketPrefix. This is basically just a workaround for what I consider to be a bug in Gatsby.