Skip to main content

Correct CORS origins

  • October 20, 2024
  • 3 replies
  • 14 views
D

Hello,

I’m currently setting up an app which consists of a backend, deployed to a monday code and a frontend packaged as one of the features of the app.

As is obvious from the title, requests are rejected by the CORS, but I can’t figure out what the correct origin is.

https://monday.com does not work
https://{accountslug}.monday.com does not work
https://*.monday.com (where * is a wildcard) does not work

But when I spin up an app on my PC and allow localhost - everything goes through. So it is not some weird routing issue.

Hence, my question. What is the correct origin of the request from one of app features?

Thank you.

3 replies

dvdsmpsn
Forum|alt.badge.img+1
  • dvdsmpsn
  • Participating Frequently
  • October 20, 2024

@dmvv some examples of the code that fails will help.

D
  • dmvv
  • Author
  • New Participant
  • October 21, 2024

The thing is, code does not fail. Server can be made to accept requests from my PC (localhost origin) or it also can be made to accept any origin, which is not an acceptable solution.

The code is as follows
image

Can’t find the right parameter for the policy.

dvdsmpsn
Forum|alt.badge.img+1
  • dvdsmpsn
  • Participating Frequently
  • October 21, 2024

I’m guessing that you could be using Asp.net or something similar. Again full code examples would be helpful.

Also, what URL are you attempting to contact and for what purpose? I’m not sure that you’d even need CORS configuring for app dev.

Terms & ConditionsCookie settingsAccessibility statement