-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
cors_allowed_origins doesn't work for http #1383
Comments
I saw a response but I think it was deleted anyway if you ask if I tried |
That's exactly what I was asking then deleted because I thought that you did it :). Do you have a small sniper maybe an HTTP request example that you use so I have a starting point? |
|
Just wanted to ask if there is anything that is missing yet from my side ? |
@obecny I tested your HTML page and the problem seems to lie in the additional header you set ( Right now there is no way that I see to allow extra headers without adding more logic to the OTLP receiver. Can you give some more info on your use case to see how generally useful it would be? |
We hit the same problem. I think what happens is that CORS AllowedHeaders needs to be exposed in |
* zc: add support for exporter_otlp_endpoint and resource_attributes in config * zc: remove otlp endpoint from install config
Describe the bug
Created a configuration like here for localhost
https://github.com/open-telemetry/opentelemetry-collector/tree/master/receiver/otlpreceiver#writing-with-httpjson
But still cors doesn't work in browser
What did you expect to see?
I expected to see at least something like this
Also Access-Control-Allow-Headers should contain all requested headers -
What did you see instead?
In OPTIONS response I see this
And cors doesn't work
What version did you use?
latest 0.6.0
What config did you use?
Environment
osx, docker
Additional context
Page is served on
http://localhost:8090/user-interaction/
I tried all different variations for
cors_allowed_origins
as well none of it workedfor example
The text was updated successfully, but these errors were encountered: