Re: WebRequest.Timeout bugs?
From: David D Webb (spivey_at_nospam.post.com)
Date: 08/23/04
- Next message: Paul G. Tobey [eMVP]: "Re: Turn on backlight"
- Previous message: Elmer Miller: "Exception Handling"
- In reply to: Jon Skeet [C# MVP]: "WebRequest.Timeout bugs?"
- Next in thread: Jon Skeet [C# MVP]: "Re: WebRequest.Timeout bugs?"
- Reply: Jon Skeet [C# MVP]: "Re: WebRequest.Timeout bugs?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 23 Aug 2004 11:28:14 -0400
I've found that if the server accepts the request, then sends back some
data, but never completes the response, the timeout MAY not trigger
properly. You may need to switch to asynchronous requests for tighter
control over the process.
-Dave
"Jon Skeet [C# MVP]" <skeet@pobox.com> wrote in message
news:MPG.1b940f1e1efe479498b26c@msnews.microsoft.com...
> I'm trying to understand why our mobile client isn't behaving
> gracefully with a "hung" server. The server is accepting web requests,
> but then not responding to them. Obviously we're working on that side
> of the problem too, but we thought that by putting a timeout on the
> WebRequest, and backing off in the same was as we do for other errors,
> that we'd have a robust system. Apparently we don't.
>
> I'm being absolutely rigorous in cleaning up - not only am I calling
> Close() on every WebResponse received (including those embedded in
> WebExceptions) but I'm also closing the ResponseStream - hopefully
> unnecessarily.
>
> The situation is slightly complicated by the server being hung in such
> a way that the first request is rejected (correctly) with a 401
> response due to the way our authentication works. (The first request
> for any client is a 401 with a nonce to use for future authentication.)
>
> The first request works fine with a suitably high timeout, although it
> *does* time out if the timeout is set very low.
>
> The second request (which the server actually hangs on) never seems to
> time out.
>
> It's as if the timeout only applies from the start of the call
> (WebRequest.GetResponse) to the time at which the connection is
> actually made.
>
> Does anyone have any idea what's going on, and how to fix it?
>
> --
> Jon Skeet - <skeet@pobox.com>
> http://www.pobox.com/~skeet
> If replying to the group, please do not mail me too
- Next message: Paul G. Tobey [eMVP]: "Re: Turn on backlight"
- Previous message: Elmer Miller: "Exception Handling"
- In reply to: Jon Skeet [C# MVP]: "WebRequest.Timeout bugs?"
- Next in thread: Jon Skeet [C# MVP]: "Re: WebRequest.Timeout bugs?"
- Reply: Jon Skeet [C# MVP]: "Re: WebRequest.Timeout bugs?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|