79316398

Date: 2024-12-29 21:41:37
Score: 1.5
Natty:
Report link

At the end it wasn't really CORS related , because if it was a CORS issue you would at least get a response . The problem was that my frontend was working over https and my backend was working over http , thus the browser was blocking the request due to a mixed content policy . The error was quite misleading especially in mozilla , (i guess chrome is a good browser to work on after all). So simply i altered the requests to be made to an endpoint on my domain and told nginx to forward them to my backend , this way the browser would have no reason to block the request from being sent.

Reasons:
  • Long answer (-0.5):
  • No code block (0.5):
  • Self-answer (0.5):
  • Single line (0.5):
  • Low reputation (0.5):
Posted by: ESvi3