Quantcast
Channel: Nginx Forum - Nginx Mailing List - English
Viewing all articles
Browse latest Browse all 7229

CORS headers not being set for a 401 response from upstream. (no replies)

$
0
0
Hi,

I am trying to setup CORS headers in my nginx config. My config is here :
http://pastie.org/private/eevpeyy6uwu25rl5qsgzyq

The upstream is defined separately.

It responds fine to OPTIONS request. It also adds the
"Access-Control-Allow-Origin *" header to responses from the upstream
(pm_puma_cluster) when the response status is 200.

But if the response status from the upstream is 401 it is not adding the
CORS header.

Is it expected? Or am I missing something in the config?

P.S : The upstream is a Rails app and I would prefer to deal with the CORS
headers in the nginx and not mess with them in the Rails app.

--
Regards,
Srirang G Doddihal
Brahmana.

The LIGHT shows the way.
The WISE see it.
The BRAVE walk it.
The PERSISTENT endure and complete it.

I want to do it all ALONE.
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Viewing all articles
Browse latest Browse all 7229

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>