Nginx proxy_intercept_errors

[Kiril Kalchev]

Yes you are right. Thank you.

On Mar 6, 2013, at 5:44 PM, Maxim Dounin wrote:

> Hello!
> 
> On Wed, Mar 06, 2013 at 04:45:33PM +0200, Kiril Kalchev wrote:
> 
>> Just for the record, I think I found a kind of solution.  It 
>> looks good if my backend returns http codes 3xx. I have tried 
>> with 333 and 334 and it looks great. I know it is an ugly hack, 
>> but my findings may help to other poor souls. I hope this 
>> behavior will not change in the next versions. 
> 
> I would suppose it works as these responses are returned with 
> "Content-Length: 0" by your backend.  As already mentioned in the 
> very first reply, connections are kept alive if it's known from 
> response headers that there is no body.
> 
> -- 
> Maxim Dounin
> http://nginx.org/en/donation.html
> 
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3565 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20130306/1e183bde/attachment.bin>