Skip to content

feat: add PaaS documentation regarding CORS origins - #2642

Open
Kevin Rudde (kevinrudde) wants to merge 1 commit into
mainfrom
paas-cors-origins
Open

Kevin Rudde (kevinrudde) wants to merge 1 commit into
mainfrom
paas-cors-origins

Conversation

@kevinrudde

Copy link
Copy Markdown
Member

Summary

Related links

Checklist

  • I reviewed affected links, code samples, and cross-references, including PageRef references where relevant.
  • I added or updated redirects in .gitbook.yaml if pages were moved, renamed, or deleted.
  • I updated .wordlist.txt (and sorted it) if spellcheck flags new legitimate terms.
  • I listed every dependent pull request that is not merged yet under Dependent PRs below.
  • Dependent changes that must be released, not only merged, before this documentation goes live have been published.
  • This pull request is ready for review.

Dependent PRs

Notes

@shopware-dev-docs-connector

shopware-dev-docs-connector Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Developer Docs healthcheck

Status: Completed with success.
Repository: shopware/docs
Commit: 3e15c27
Preview: https://developer-documentation-601qoij86-shopware-frontends.vercel.app
Workflow run: #5869

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 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

@kevinrudde
Kevin Rudde (kevinrudde) force-pushed the paas-cors-origins branch 2 times, most recently from f13aa80 to 5843c68 Compare October 23, 2026 15:36
@kevinrudde
Kevin Rudde (kevinrudde) marked this pull request as ready for review October 23, 2026 15:44
@kevinrudde
Kevin Rudde (kevinrudde) requested a review from a team October 23, 2026 15:44
@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

📢 Developer Announcement Recommendation

Recommendation: ⚠️ Manual Review Required

Some changed file paths match announcement categories, but the PR title/body does not provide enough evidence for an automatic recommendation.

High-Confidence Signals

  • ✅ New Developer Documentation Article — Adds a new developer guide, tutorial, reference, example, or learning resource.
    • Matching files: products/paas/shopware/cdn/cors-origins.md

Signals Requiring Manual Review

  • ⚠️ Configuration and Environment Requirements — Changes environment variables, configuration options, dependencies, or deployment requirements.
    • The changed file path matches this category, but the PR title/body does not provide enough keyword evidence for an automatic recommendation.
    • Matching files: products/paas/shopware/cdn/cors-origins.md, products/paas/shopware/cdn/index.md

This recommendation is based on changed file paths and the PR title/body. Review the actual changes before publishing a community announcement.

@sushmangupta Su (sushmangupta) added the new Label for new content that is published in the changelog label Oct 27, 2026

### 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:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you about that, the point of this is also to have Fastly responding to preflight requests instead of the origin?

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

Labels

new Label for new content that is published in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants