HttpWebRequest timeouts

[Glenn]

Hi

I'm trying to building something to check the availability of a web page.

The code is using a HttpWebRequest, bypassing our proxy server and hitting
both HTTP/HTTPS pages. Initially I get a HTTP response code of 200. After
the second or third attempt at hitting the same page over a period of a
couple of minutes, I get a timeout. Note that I'm creating a fresh
HttpWebRequest each time I hit the web page.

I restart the console app and it works, but again, only for a couple of
attempts.

Any ideas?

Thanks

Glenn

Code below...
public override bool RunTest()

{

bool success = false;

HttpWebRequest request = WebRequest.Create( WebSiteProperties.WebSiteUrl )
as HttpWebRequest;

request.CachePolicy = new HttpRequestCachePolicy(
HttpRequestCacheLevel.BypassCache );

try

{

HttpWebResponse response = request.GetResponse() as HttpWebResponse;

HttpStatusCode responseHttpStatusCode = response.StatusCode;

List<stringexpectedHttpStatusCodes = new List<string>(

WebSiteProperties.ExpectedHttpStatusCodes.Split( ",".ToCharArray(),
StringSplitOptions.RemoveEmptyEntries ) );

success = expectedHttpStatusCodes.Contains( (
(int)responseHttpStatusCode ).ToString() );

return success;

}

catch ( Exception exception )

{

return success;

}

}

[Matt Lacey]

On 5 Mar, 15:18, "Glenn" <[e-mail]:

Hi

I'm trying to building something to check the availability of a web page.

The code is using a HttpWebRequest, bypassing our proxy server and hitting
both HTTP/HTTPS pages. Initially I get a HTTP response code of 200. After
the second or third attempt at hitting the same page over a period of a
couple of minutes, I get a timeout. Note that I'm creating a fresh
HttpWebRequest each time I hit the web page.

I restart the console app and it works, but again, only for a couple of
attempts.

Any ideas?

Thanks

Glenn

Code below...
public override bool RunTest()

{

bool success = false;

HttpWebRequest request = WebRequest.Create( WebSiteProperties.WebSiteUrl )
as HttpWebRequest;

request.CachePolicy = new HttpRequestCachePolicy(
HttpRequestCacheLevel.BypassCache );

try

{

HttpWebResponse response = request.GetResponse() as HttpWebResponse;

HttpStatusCode responseHttpStatusCode = response.StatusCode;

List<stringexpectedHttpStatusCodes = new List<string>(

WebSiteProperties.ExpectedHttpStatusCodes.Split( ",".ToCharArray(),
StringSplitOptions.RemoveEmptyEntries ) );

success = expectedHttpStatusCodes.Contains( (
(int)responseHttpStatusCode ).ToString() );

return success;

}

catch ( Exception exception )

{

return success;

}
}- Hide quoted text -

- Show quoted text -

I haven't got the code to hand but I've had something like this in the
past.
I think it comes down to not closing/disposing the HttpWebResponse
object.

[Glenn]

Problem solved.

I should have closed the damn response stream, damn, damn, damn, damn it!

Glenn

"Glenn" <gl**********@yahoo.co.ukwrote in message
news:OA**************@TK2MSFTNGP05.phx.gbl...

Hi

I'm trying to building something to check the availability of a web page.

The code is using a HttpWebRequest, bypassing our proxy server and hitting
both HTTP/HTTPS pages. Initially I get a HTTP response code of 200.
After the second or third attempt at hitting the same page over a period
of a couple of minutes, I get a timeout. Note that I'm creating a fresh
HttpWebRequest each time I hit the web page.

I restart the console app and it works, but again, only for a couple of
attempts.

Any ideas?

Thanks

Glenn

Code below...
public override bool RunTest()

{

bool success = false;

HttpWebRequest request = WebRequest.Create( WebSiteProperties.WebSiteUrl )
as HttpWebRequest;

request.CachePolicy = new HttpRequestCachePolicy(
HttpRequestCacheLevel.BypassCache );

try

{

HttpWebResponse response = request.GetResponse() as HttpWebResponse;

HttpStatusCode responseHttpStatusCode = response.StatusCode;

List<stringexpectedHttpStatusCodes = new List<string>(

WebSiteProperties.ExpectedHttpStatusCodes.Split( ",".ToCharArray(),
StringSplitOptions.RemoveEmptyEntries ) );

success = expectedHttpStatusCodes.Contains( (
(int)responseHttpStatusCode ).ToString() );

return success;

}

catch ( Exception exception )

{

return success;

}

}

[Glenn]

Thanks Matt

Yep, you're right, although HttpWebRequest and it's response counterpart
don't implement IDisposable, you have to remember to close the streams, and
definately don't cross them ;-).

Time for the pub I think.

Glenn

"Matt Lacey" <m.*****@fdsltd.co.ukwrote in message
news:11**********************@n33g2000cwc.googlegr oups.com...

On 5 Mar, 15:18, "Glenn" <[e-mail]:

>Hi

I'm trying to building something to check the availability of a web page.

The code is using a HttpWebRequest, bypassing our proxy server and
hitting
both HTTP/HTTPS pages. Initially I get a HTTP response code of 200.
After
the second or third attempt at hitting the same page over a period of a
couple of minutes, I get a timeout. Note that I'm creating a fresh
HttpWebRequest each time I hit the web page.

I restart the console app and it works, but again, only for a couple of
attempts.

Any ideas?

Thanks

Glenn

Code below...
public override bool RunTest()

{

bool success = false;

HttpWebRequest request = WebRequest.Create(
WebSiteProperties.WebSiteUrl )
as HttpWebRequest;

request.CachePolicy = new HttpRequestCachePolicy(
HttpRequestCacheLevel.BypassCache );

try

{

HttpWebResponse response = request.GetResponse() as HttpWebResponse;

HttpStatusCode responseHttpStatusCode = response.StatusCode;

List<stringexpectedHttpStatusCodes = new List<string>(

WebSiteProperties.ExpectedHttpStatusCodes.Split ( ",".ToCharArray(),
StringSplitOptions.RemoveEmptyEntries ) );

success = expectedHttpStatusCodes.Contains( (
(int)responseHttpStatusCode ).ToString() );

return success;

}

catch ( Exception exception )

{

return success;

}
}- Hide quoted text -

- Show quoted text -

I haven't got the code to hand but I've had something like this in the
past.
I think it comes down to not closing/disposing the HttpWebResponse
object.

[Jon Skeet [C# MVP]]

Glenn <gl**********@yahoo.co.ukwrote:

Yep, you're right, although HttpWebRequest and it's response counterpart
don't implement IDisposable, you have to remember to close the streams, and
definately don't cross them ;-).

WebResponse implements IDisposable, but WebRequest doesn't.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Glenn]

Ah, didn't notice that.

Thanks

"Jon Skeet [C# MVP]" <sk***@pobox.comwrote in message
news:MP************************@msnews.microsoft.c om...

Glenn <gl**********@yahoo.co.ukwrote:

>Yep, you're right, although HttpWebRequest and it's response counterpart
don't implement IDisposable, you have to remember to close the streams,
and
definately don't cross them ;-).

WebResponse implements IDisposable, but WebRequest doesn't.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too