Skip to content

in_http: add changes for cors_allow_origins on v1.19.0 #574

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.

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

Draft
wants to merge 1 commit into
base: 1.0
Choose a base branch
from

Conversation

daipom
Copy link
Contributor

@daipom daipom commented Mar 26, 2025

@daipom
Copy link
Contributor Author

daipom commented Mar 26, 2025

This should be merged after v1.19.0 release.

daipom pushed a commit to fluent/fluentd that referenced this pull request Mar 26, 2025
**Which issue(s) this PR fixes**: 

**What this PR does / why we need it**: 
Some requests, such as those made by apps, certain automated scripts, or
older browsers, may not include an Origin header. Previously, such
requests were blocked by the CORS check, even though they may not
necessarily be cross-origin.

For CORS, the server is responsible for reporting the allowed origins.
The web browser is responsible for enforcing that requests are only sent
from allowed domains. So this change updates the CORS handling logic to
allow requests with an empty Origin header to pass, ensuring
compatibility with legitimate non-browser clients while maintaining
security.

**Docs Changes**:
fluent/fluentd-docs-gitbook#574

**Release Note**: 
The same as the title.

Signed-off-by: Richard Lee <[email protected]>
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.

1 participant