views:

2351

answers:

3

Hi, I'm trying to understand where I can configure a request timeout for all requests arriving to a servlet of mine (or all of my servlets)? Is that, as I think, a container property? Also, how does this affect different browsers? Do they all comply to the parameter the container dictates? Or maybe the request timeout time isn't even something I can control and each browser decides on this on its own? (Just to be clear I'm not talking about session timeout)

TIA Ittai

+2  A: 

The timeout from a client (i.e. how long it waits for a response to an HTTP request) is determined at the client. For IE, see this, and for Firefox see this.

You can't control this timeout from the server.

Vinay Sajip
First of all thank you for the reply, this cannot be changed programatically on the client side (via JavaScript) right?
Ittai
I don't believe so, no.
Vinay Sajip
A: 

You cannot control the client timeout from the server. However you may be able to send data back to the client every now and then while your long running operation is busy. This will prevent the client from timing out and can be used to display progress to the user etc. Write data to the OutputStream or Writer obtained from the response and call flush to send partial data to the client.

David Tinker
how can this partial data be obtained if using xmlHttpRequest?I've read than in IE you cannot access the data until the request is finished
Ittai
Yes, but the client shouldn't time out as long as some data is coming in.
Vinay Sajip
You're right but It's a bit more complicated because I'm implementing Comet so I'll either use 'Long Polling' and thus will need a longer timeout to save requests or use Streaming which is what I though David was suggesting. Anyway thank you.
Ittai
+1  A: 

Even though you can't control client timeout, you can make server very impatient :) For example, on Tomcat, you can do this in your connector,

<Connector port="8080"  
  ...
  timeout="50000"
  disableUploadTimeout="false" />

This makes server only wait 5 seconds and close the connection. Browser will get a connection closed error. You can treat it the same as timeout in client.

Of course, this only works if the timeout is caused by the server, not connectivity issues between browser and server.

ZZ Coder