[dev] forcing a browser to open a new connection

Manlio Perillo manlio_perillo at libero.it
Thu Oct 18 00:49:43 MSD 2007

Igor Sysoev ha scritto:
> On Wed, Oct 17, 2007 at 08:49:30PM +0200, Manlio Perillo wrote:
>> Igor Sysoev ha scritto:
>>> On Wed, Oct 17, 2007 at 08:23:41PM +0200, Manlio Perillo wrote:
>>>> What is the best method for forcing a browser to close the current 
>>>> connection and to open a new connection?
>>>> Now I'm using the Refresh headers.
>>> r->keepalive = 0;
>> Here is, in detail, what I want to do (again, for mod_python).
>> 1) A browser requests a resource (WSGI application)
>> 2) mod_python detects that the Python script has changed,
>>    and (if enabled) raises the SIGQUIT signal, so that a new process can
>>    be created, that will load the updated WSGI application
>> 3) I need to tell the brower to make a new request, so that it will use
>>    the updated script
> Refresh is no standard way, but as I know it is supported by all browsers.

Ok, thanks.
I have tried to return 503 Service Unavailable, with a Retry-After: 0 
header, but Firefox does not support this.

Another solution is to use the Location header with a 3xx response.

Regards  Manlio Perillo

More information about the nginx mailing list