Note that there are some explanatory texts on larger screens.

plurals
  1. USrobert.bo.roth
    primarykey
    data
    text
    plurals
    1. COThis problem doesn't really make much sense. I understand CORS, and I've had my server setup and running fine for months as is without any issues. Our current development, staging, and live servers are working right now, with the same code and server setup that I have. I have 3 other developers who have the same setup, and theirs is working fine. My local environment is the ONLY one that has this issue, and I guarantee you it has nothing to do with my understanding of CORS.
      singulars
    2. COI can't even send with the Access-Control-Allow-Origin header on my POST request because the browser isn't getting the correct `Access-Control-Allow-Headers` after I've added allow-origin to the allowed headers.
      singulars
    3. COSince when? And why do other computers making the same call not have to send that header? The bigger issue at hand is that when I'm updating my server response code, to send different response headers (like sending the exact origin rather than the wildcard '*'), I'm still getting the same headers back. It's almost as if my computer has cached the OPTIONS response and isn't using the real data I'm sending from my local server. I've had other developers try the same request from their computers, directed at my local network IP, and they get the correct headers and their requests don't fail.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload