Skip to content
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

🐛 Bug Report: Http headers issue #6644

Open
2 tasks done
drynau-gdhub opened this issue Oct 7, 2024 · 2 comments
Open
2 tasks done

🐛 Bug Report: Http headers issue #6644

drynau-gdhub opened this issue Oct 7, 2024 · 2 comments
Labels

Comments

@drynau-gdhub
Copy link

drynau-gdhub commented Oct 7, 2024

📜 Description

I have

  1. novu service v0.24.0 (https://novu-api.some-domain.com)
  2. my next.js application (https://staging.app.some-domain.com)

I use @novu/react and Inbox for showing user notifications from novu service (1).
And get a CORS error

Access to fetch at 'https://novu-api.some-domain.com/v1/inbox/session' from origin 'https://staging.app.some-domain.com' has been blocked by CORS policy: Request header field novu-api-version is not allowed by Access-Control-Allow-Headers in preflight response.

👟 Reproduction steps

  1. Deploy novu with Docker on AWS EC2.
  2. Deploy my next.js application on AWS ECS.
  3. Try show notification in the app. The app is showing widget.
  4. I have the error on an endpoint: novu-api.some-domain.com/v1/inbox/session. Other API endpoints are working correctly.

👍 Expected behavior

Return OK on novu-api.some-domain.com/v1/inbox/session and show my notifications.

👎 Actual Behavior with Screenshots

image

Novu version

0.23.0, 0.24.0

npm version

No response

node version

No response

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

  • I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

Are you willing to submit PR?

None

Copy link

linear bot commented Oct 7, 2024

@mustansirgodhrawala
Copy link

Is this getting fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants