Welcome! Log In Create A New Profile

Advanced

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

July 15, 2014 01:37PM
Thanks Maxim for the documentation link.

I am running into a similar issue. But it is for a 504 server time out.

I'm doing a long-poll, but it is a cross domain long poll GET request. The client implementation is trying to use CORS.
It all works fine with when the GET requests returns something.
But when the server times out (HTTP 504) there is no CORS header information on the reply and the client code treats it as:
'No 'Access-Control-Allow-Origin' header is present on the requested resource'

Just extending the keepalive_timeout indefinitely is also not a good idea.

So what is the recommended way to handle a 504. It seems I don't get this in the client side XmlHttpRequest. The exceptions occurs before.
Subject Author Posted

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

Srirang Doddihal June 09, 2014 07:06AM

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

Maxim Dounin June 10, 2014 07:34AM

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

ensing July 15, 2014 01:37PM

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

Maxim Dounin July 15, 2014 06:22PM

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

manimalcruelty August 21, 2015 01:30PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 160
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready