# Retrying proxy connect timeouts but not read timeouts

**URL:** <https://www.ruby-forum.com/t/retrying-proxy-connect-timeouts-but-not-read-timeouts/212434>\
**Category:** NGINX\
**Created:** [October 3, 2011, 12:08am UTC](https://www.ruby-forum.com/t/retrying-proxy-connect-timeouts-but-not-read-timeouts/212434 "2011-10-03T00:08:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\
**Post date:** [October 3, 2011, 12:08am UTC](https://www.ruby-forum.com/t/retrying-proxy-connect-timeouts-but-not-read-timeouts/212434/1 "2011-10-03T00:08:18Z")

</div>

I’ve got a proxy + upstream setup with three defined upstream  
servers. I would like nginx to retry requests when there is an error  
or when there is a connection timeout (but not a read timeout).  
However, it appears that proxy\_next\_upstream only has the granularity  
of “error” and “timeout”.

Is there any way to have proxy\_next\_upstream differentiate between  
connection timeout and read timeout? If not, is creating a ticket in  
the bug tracker the proper way to request such a feature?

Thanks,  
Gary