Skip to content

fix: serve docs assets from the same origin as pages#570

Open
ivanauth wants to merge 1 commit into
authzed:mainfrom
ivanauth:fix/issue-478-single-asset-domain
Open

fix: serve docs assets from the same origin as pages#570
ivanauth wants to merge 1 commit into
authzed:mainfrom
ivanauth:fix/issue-478-single-asset-domain

Conversation

@ivanauth

@ivanauth ivanauth commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Fixes #478.

Docs pages are served from authzed.com/docs but their assets (JS/CSS/fonts) were loaded from a second domain (docs-authzed.vercel.app) via assetPrefix, which breaks for users behind restrictive firewalls.

Removes the production assetPrefix (and the crossOrigin: "anonymous" that only existed to support the cross-origin CDN).

The production assetPrefix pointed at docs-authzed.vercel.app, so pages
loaded from authzed.com pulled their assets from a second domain, which
breaks for users behind restrictive firewalls. The authzed.com rewrite
already proxies everything under /docs, including /docs/_next/static
assets, so the prefix is unnecessary: relative asset URLs resolve
same-origin through the existing rewrite.

With no cross-origin asset domain left, the crossOrigin setting added
for the CDN domain is no longer needed either.
@github-actions

Copy link
Copy Markdown
Contributor

Preview deployment skipped — @ivanauth does not have write access to this repository.

A maintainer can trigger a preview deployment by re-running this workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs are serving assets from two different domains

1 participant