-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Issues with in_http plugin while using CORS #1701
Comments
Does your application send Origin header to |
I got it working following in_logtank_http plugin [https://github.com/logTank/fluent-plugin-http/blob/master/lib/fluent/plugin/in_logtank_http.rb] Following lines were important to get the CORS issue resolved:
Earlier I tried sending headers
|
So porting above code from logtank's fluent-plugin-http resolve this issue, right? |
This issue is still present in the latest td-agent. |
Actually i´m facing the same issue,
On the fluentd server side i have (fluentd.conf) : But when i run the web app, i get this error : it´s supposed that with the Client and Server config it will work.. Thanks in advanced |
Does anyone check |
I checked logtank http and diff is small, so I simply apply changes to
|
@gma-git-admin @tjratch @wilesna25 This issue should be resolved in Fluentd v1.3.0. |
@fujimotos , I am running td-agent 1.4.2 (3.4.1) and can confirm this fix works! Thank you! |
seems to be solved. closed |
@ganmacs Thank you! |
http://dev.myapp.com:8282/app.RouteChange
This throws following error:
OPTIONS http://dev.myapp.com:8282/app.RouteChange 400 (Bad Request)
XMLHttpRequest cannot load http://dev.myapp.com:8282/app.RouteChange. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://dev.myapp.com' is therefore not allowed access. The response had HTTP status code 400.
The text was updated successfully, but these errors were encountered: