Last post Nov 02, 2011 04:22 PM by gerrylowry
Nov 01, 2011 01:16 AM|yhemanth|LINK
On our website, we are finding out users who sometimes seem to make a lot of requests to our aspx pages and disconnect prematurely. We would like to discard these requests without processing them and thus improve website performance. One of the approaches
recommended seems to be to use the HttpResponse.IsClientConnected property.
While this is working perfectly on IIS 7, the same does not seem to work on IIS 6 on Windows Server 2003 SP 2. We are using ASP.NET 3.5. Is this a known issue ?
Nov 02, 2011 04:22 PM|gerrylowry|LINK
FWIW: (iis 5, not 6 ... do not know if it's a 6 problem too)
also, imho, if the request is not likely to be expensive, it may be better to complete the request ... of course, for that, you need some way to separate inexpensive requests from expensive ones. while you can shorten the connect time timeout, i'm not sure
whether there is any way to specify how much time to allow beyond the connection ... alternatively, you could limit the number of rows returned.