Repository navigation
feat: add PaaS documentation regarding CORS origins - #2642
Kevin Rudde (kevinrudde) wants to merge 1 commit into
Conversation
Developer Docs healthcheckStatus: Completed with |
There was a problem hiding this comment.
🔵 Needs a closer look
The documented CLI commands and platform-specific Fastly behavior need maintainer confirmation against their implementations.
No open issues 🎉
What changed in this PR
Adds CORS-origin guidance to the Shopware PaaS Native CDN documentation.
Changes:
- Documents CLI commands, origin requirements, and deployment timing.
- Explains CDN and storefront behavior, verification, and troubleshooting.
- Links the new guide from the CDN overview.
| File | Description |
|---|---|
| products/paas/shopware/cdn/index.md | Links to the CORS origins guide. |
| products/paas/shopware/cdn/cors-origins.md | Adds CORS configuration and troubleshooting guidance. |
Review effort: Balanced
f13aa80 to
5843c68
Compare
📢 Developer Announcement RecommendationRecommendation: Some changed file paths match announcement categories, but the PR title/body does not provide enough evidence for an automatic recommendation. High-Confidence Signals
Signals Requiring Manual Review
|
5843c68 to
cf67df2
Compare
|
|
||
| ### Storefront | ||
|
|
||
| For the storefront, Fastly answers CORS at the edge for the paths `/admin` and `/bundles`. These paths serve static files, such as the files of the Administration and the public assets of plugins. Browsers only load some of these files from another origin when CORS allows it, for example scripts loaded as modules and fonts. Fastly answers CORS for them like this: |
There was a problem hiding this comment.
Are you about this path, our tests shown that Fastly respond to preflight requests for any paths?
| Shopware PaaS Native manages this for you with CORS origins. You add the origins of the sites that are allowed to call your application, and the platform configures the storefront, the CDN, and the public bucket accordingly. | ||
|
|
||
| ::: info | ||
| CORS origins are not needed for the Shopware API. Shopware allows cross-origin requests to its API routes, such as `/store-api`, from any origin by default, so a composable frontend can call them without adding an origin. See [CORS troubleshooting](https://developer.shopware.com/frontends/resources/troubleshooting/CORS.html) in the Shopware Frontends documentation. |
There was a problem hiding this comment.
Are you about that, the point of this is also to have Fastly responding to preflight requests instead of the origin?
cf67df2 to
3e15c27
Compare
Summary
Related links
Checklist
PageRefreferences where relevant..gitbook.yamlif pages were moved, renamed, or deleted..wordlist.txt(and sorted it) if spellcheck flags new legitimate terms.Dependent PRs
Notes