Hi! As suggested by <@U01GCJKA8P9>, I'm going to s...
# random
w
Hi! As suggested by @big-carpet-38439, I'm going to share my use case here. It's probably very simple and I'm just a little too tired 😂 but it's okay, I'll share anyway. Essentially for the project I'm working on we deployed datahub (not me, someone else). And so I thought it would be cool to visualize the datasets in a React web app. So, I created an access token, added that to my header. But sadly I keep getting the dreaded CORS error. (For context, I'm new to basically every techno I'm using. Wanted to try out some new things 🥰)
g
CORS error is blocked because it's a security risk: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors You're hitting a service that's not in the same domain(i.e. not localhost). If you're just testing locally, you can start chrome in unsecure mode(not recommended). Or use a nginx proxy or similar to create a proxy pass to your deployed datahub endpoint
a
@gorgeous-dinner-4055 im the one who made the deployment . is there a configuration in the helm chart to allow more origins ?
g
We don't use the helm charts at our company, so I'm not totally sure whats there, but i'd be surprised if there is any config in the helm chart to allow this feature as it's deploy/company specific. If you're doing this locally, you can modify the docker-compose and add a proxy pass pretty easily using something like nginx.
a
thanks a lot 🙂
c
@average-alligator-6750 Did you manage to allow origins? I am facing the same issue. I would appreciate your configurations since we’re unable to make it work.