Skip to content

Custom headers in Cloud rewrite rules #739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AugustMiller merged 1 commit into from
Oct 24, 2025
Merged

Custom headers in Cloud rewrite rules #739

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/cloud/redirects.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,3 +127,18 @@ rewrites:
pathname: '/(favicon.ico|.well-known|dist)/*?'
destination: '{artifactBaseUrl}/{request.uri}'
```

### Custom Headers <Since ver="2.16.0" repo="craftcms/cloud-extension-yii2" product="Cloud extension" description="The ability to set custom headers in rewrite rules was added in {product} {ver}." :use-changelog="false" />

You can set arbitrary HTTP headers on any rewritten response by including a key-value map under a `headers` key:

```yml
rewrites:
- pattern:
pathname: '/dist/js/*'
destination: '{artifactBaseUrl}/{request.uri}'
headers:
Access-Control-Allow-Origin: 'https://mydomain.com'
```

Headers are combined with those from the `destination`, overwriting any shared names.