#Permanent redirects in SSR

5 messages · Page 1 of 1 (latest)

marsh mantleBOT
#

Hi @brazen forum. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

The code you provided seems to have a small syntax error. The destination string has an extra double quote at the end. Here's the corrected code:

export default defineConfig({
    redirects: {
        "/blog/[...slug]": {
            status: 302,
            destination: '/posts/[...slug]',
        },
    },
});

This code will set up a redirect from /blog/[...slug] to /posts/[...slug] with a status code of 302. This means that any URL that matches the pattern /blog/[...slug] will be redirected to /posts/[...slug].

Remember that both the old and new routes must contain the same parameters. In this case, the [...slug] parameter must be present in both routes.

Also, note that the status code is 301 by default. If you're building to HTML files, the status code is not used by the server. However, when using SSR or a static adapter, you can specify the status code in addition to the new destination as you've done in your code.

For Cloudflare, you need to place the _redirects file in your Astro project’s public/ directory. Cloudflare looks for _headers, _redirects, and _routes.json files in your build output directory to configure these features.

Sources:

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@steady meteor kapa.ai is still learning and improving, please let us know how it did by reacting below

#

Let me check the knowledge base for you. One moment! :books:

#

The error message you're seeing suggests that the redirect rule you've provided is not valid. The rule /blog/* 200 is not a valid redirect rule because it lacks a destination URL.

In Astro, you can specify a mapping of permanent redirects in your Astro config with the redirects value. For most redirects, this is a mapping of an old route to the new route. Here's an example:

export default defineConfig({
 redirects: {
 '/old-page': '/new-page'
 }
});

In your case, you should replace /old-page with /blog/* and /new-page with the new route you want to redirect to.

However, it's important to note that Astro's redirect configuration might not directly translate to Cloudflare's _redirects file. Cloudflare looks for _headers, _redirects, and _routes.json files in your build output directory to configure these features.

You might need to manually create a _redirects file in your public/ directory with the correct Cloudflare redirect syntax. Here's an example of what a line in that file might look like:

/blog/*  /new-page  301

This will redirect all routes that match /blog/* to /new-page with a status code of 301.

Sources:

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: