Forum Discussion

Newbie1's avatar
Newbie1
Occasional Contributor
3 years ago

Swagger behind Nginx Proxy and CORS error

Hi all! I have a problem. I would like to not get an CORS error after pasting in swagger available under swagger.example.com the link to the file available under testing.example.com/plik.yaml. The v...
Swagger UI
ponelat's avatar
ponelat
Staff

Newbie1 That's addressed a CORS issue, since the error appears to be from the server (unregistered device doesn't sound like any browser/web api error).

 

To support Authorization headers, you need to change from `*` to an explicit origin. You can confirm by trying a hardcoded one, and if that works you can figure out how to make it dynamic (with nginx).

 

Replace all instances with this...

add_header Access-Control-Allow-Origin: 'docs.swagger.example.com' always;

 

Newbie1's avatar
Newbie1
Occasional Contributor
3 years ago

Thank you ponelat . 🙂 I am going to ask backend devs what does mean this error. I hope I reached the end. I will let you know.

 

PS

Is it possible to do some kind of reset origin header? On one testing server I have an error from cors 

 

has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values 'https://swagger.example.com, https://swagger.example.com', but only one is allowed.

 

 but in config I have currently only one occurence of this header. Is it possible that origin header is remembered due to this:

 

add_header 'Access-Control-Max-Age' 17286000;