P.S.: Clerk.com is doing something similar by the way .

Have you tried using a proxy rewrite instead of a redirect?

hey, sorry for the late response. I'm only just getting back to my PC now.

I've not used proxy rewrite, I only just tried using https://vercel.com/docs/edge-network/rewrites

Hi, @irorochad!

From what I can see, your configuration rewrote the main document requests but didn't properly handle the associated static assets which led to a functional but unstyled documentation page. This is why you saw the content of your docs but without the correct styling and potentially missing some functionality provided by JavaScript files.

You'll need to update your vercel.json file to add a second rewrite rule specifically for static assets and include a headers configuration for security. I've shared an example below, what it does is rewrites main content requests from /docs to docs.maindomain.com and static asset requests (in the /_next directory) to the correct location on docs.maindomain.com.

1
{
2
  "rewrites": [
3
    {
4
      "source": "/docs/:path*",
5
      "destination": "https://docs.maindomain.com/:path*"
6
    },
7
    {
8
      "source": "/docs/_next/:path*",
9
      "destination": "https://docs.maindomain.com/_next/:path*"
10
    }
11
  ],
12
  "headers": [
13
    {
14
      "source": "/docs/(.*)",
15
      "headers": [
16
        {
17
          "key": "X-Frame-Options",
18
          "value": "SAMEORIGIN"
19
        }
20
      ]
21
    }
22
  ]
23
}

After updating and deploying this configuration, your documentation should load correctly, including all styles and static assets. If issues persist, verify your documentation site setup, check for absolute URLs, and clear your browser cache.

Let us know how you get on!

Thank you @pawlean . The solution did work well. I noticed that the error is from the docs configuration. I've fixed it. Thanks!

Great to hear, @irorochad!

Feel free to drop in https://community.vercel.com/c/community/4 and share what you're building by the way

Vercel Community

Discussions

Join in conversations, share opinions, and brainstorm with other community members

Oh, and thanks @josesanchez54 for jumping in here as well!