You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow deploying custom supported domains for CORS proxy (#54)
## Motivation for the change, related issues
We need a CORS proxy that supports Playground website origins other than
playground.wordpress.net.
## Implementation details
This PR updates the CORS proxy deployment workflow to conditionally
declare a list of origins supported by the CORS proxy.
## Testing Instructions (or ideally a Blueprint)
- Manually deploy to a CORS proxy test site without the new
CUSTOM_SUPPORTED_ORIGINS_SPACE_SEPARATED secret created
- Confirm the proxy works with requests from origin
`https://playground.wordpress.net`
- Add the CUSTOM_SUPPORTED_ORIGINS_SPACE_SEPARATED secret
- Manually deploy to a CORS proxy test site
- Make HTTP requests to the CORS proxy with an Origin header containing
a supported origin and confirm success
- Make HTTP requests to the CORS proxy with an Origin header containing
a unsupported origin and confirm failure
0 commit comments