Hi Willy I am sure I want the client timeout :-)
One hostname is for normal http connections, which should disconnect after a short period of client inactivity. The other hostname is for websockets, which need to be held open even if the client (or server for that matter) sends no data for a long period of time. Laurie On 19 April 2010 20:53, Willy Tarreau <[email protected]> wrote: > On Mon, Apr 19, 2010 at 11:13:48AM +0100, Laurie Young wrote: > > Hi Chris > > > > This would do what I want, expcet the timeout client directive does not > work > > within a backend block. :-( > > I'm really not sure it's the client timeout you want to set based on the > host name, rather it should be the server timeout, isn't it ? There should > be no reason to have short and long client timeouts based on a URL or such, > as a client timeout is only related to the client. I really think you want > to adjust the server's response time, in which case "timeout server" will > work in your backends. > > Willy > > -- Dr Laurie Young Scrum Master New Bamboo Follow me on twitter: @wildfalcon Follow us on twitter: @newbamboo Creating fresh, flexible and fast-growing web applications is our passion. 3rd Floor, Gensurco House, 46A Rosebery Avenue, London, EC1R 4RP http://www.new-bamboo.co.uk
