CORS headers not being set for a 401 response from upstream.

Maxim Dounin mdounin at mdounin.ru
Tue Jun 10 11:33:43 UTC 2014


Hello!

On Mon, Jun 09, 2014 at 04:35:31PM +0530, Srirang Doddihal wrote:

> 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?

Quote from http://nginx.org/r/add_header:

"Adds the specified field to a response header provided that the 
response code equals 200, 201, 204, 206, 301, 302, 303, 304, or 
307."

-- 
Maxim Dounin
http://nginx.org/



More information about the nginx mailing list