Skip to content

Conversation

@daipom
Copy link
Contributor

@daipom daipom commented Mar 26, 2025

fluent/fluentd#4866

Signed-off-by: Daijiro Fukuda <fukuda@clear-code.com>
@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 <14349+dlackty@users.noreply.github.com>
@daipom daipom added the pending To be done in the future label Jun 25, 2025
@daipom daipom marked this pull request as ready for review June 25, 2025 05:27
@daipom daipom removed the pending To be done in the future label Jul 30, 2025
@daipom daipom requested review from Watson1978 and kenhys July 30, 2025 08:05
Copy link
Contributor

@Watson1978 Watson1978 left a comment

Choose a reason for hiding this comment

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

👍🏻

@daipom daipom merged commit 02ff4f9 into fluent:1.0 Jul 30, 2025
2 checks passed
@daipom daipom deleted the in_http-cors_allow_origins-v1.19.0 branch July 30, 2025 08:13
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.

2 participants