Skip to content

/ winston-loggly-bulk

forked from winstonjs/winston-loggly
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

Jump to bottom

Using Loggly with winston in browser is causing CORS issue #46

Closed
satgrocks opened this issue Nov 16, 2018 · 1 comment
Closed

Using Loggly with winston in browser is causing CORS issue #46

satgrocks opened this issue Nov 16, 2018 · 1 comment

Comments

@satgrocks
Copy link

@satgrocks satgrocks commented Nov 16, 2018

Getting CORS errors in browser when using loggly with winston from browser.

OPTIONS https://logs-01.loggly.com/inputs/customerToken 405 (Method Not Allowed)

Access to fetch at 'https://logs-01.loggly.com/inputs/customerToken' from origin 'https://mydomain.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
@satgrocks satgrocks changed the title Useing Loggly with winston in browser is causing CORS issue Using Loggly with winston in browser is causing CORS issue Nov 16, 2018
@satgrocks
Copy link
Author

@satgrocks satgrocks commented Dec 26, 2018

Started working after setting isBulk flag to true during setup.
@satgrocks satgrocks closed this Dec 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@satgrocks
You can’t perform that action at this time.