Net.WebRequest - Close Connection

[Jack]

I have a WebRequest object that I use to log into a site and then post some
XML. In doing this I set the KeepAlive = true so that it maintains the
connection and does operates undo the initial login.

Is there a way to force this connection to close after I an done with it.
What happens is that I may need to post the XML in several chunks due to
size therefore I cannot set the KeepAlive to False when I post the XML and
the way the code runs I do not know which pass is the last.

What happens is that the first post works fine but subsequent posts time
out, I assume this is due to the connection timing out.

Any ideas, or a better way to do this?

Jack

[Cor Ligthert [MVP]]

Jack,

In my idea is this typical a question for the newsgroup

microsoft.publi c.dotnet.framew ork.aspnet

Just an advice of course feel free what you do with it.

Cor

"Jack" <So********@new sgroups.nospams chree
f in bericht news:eS******** ******@TK2MSFTN GP06.phx.gbl...

>I have a WebRequest object that I use to log into a site and then post some
XML. In doing this I set the KeepAlive = true so that it maintains the
connection and does operates undo the initial login.

Is there a way to force this connection to close after I an done with it.
What happens is that I may need to post the XML in several chunks due to
size therefore I cannot set the KeepAlive to False when I post the XML and
the way the code runs I do not know which pass is the last.

What happens is that the first post works fine but subsequent posts time
out, I assume this is due to the connection timing out.

Any ideas, or a better way to do this?

Jack

[Walter Wang [MSFT]]

Hi Jack,

From your post title and first part, your question seems to "how to force
the connection close".

By default, HttpWebRequest. KeepAlive is true. So the connections should be
reused from one request to the next. And I don't think you need to
explicitly close the connection, just dispose the HttpWebRequest object.

Also, note that the server could also be closing the connection after
serving each request. Keep-alive can be set in the http request header, but
server can decide whether or not to reuse the connection.

Reusing connection is to improve performance. I don't think it's required
to maintain the login credential. As long as you are using the same
HttpWebRequest object, the credential should be used in subsequent
requests.

As your last question about "subsequent posts time out", I think this is
probably because the request size limit. If your server is written in
ASP.NET, the default maximum request size is 4MB. You can change this limit
in web.config:

<system.web>
<httpRuntime maxRequestLengt h="10240" /<!-- change to 10MB -->

http://msdn2.microsoft.com/en-us/library/e1f13641.aspx

maxRequestLengt h:

Specifies the limit for the input stream buffering threshold, in KB.
This limit can be used to prevent denial of service attacks that are
caused, for example, by users posting large files to the server.

Also, you can use WebClient to do the post:
http://msdn2.microsoft.com/en-us/library/tt0f69eh.aspx

If my assumption is not the case, I think a repro project would be very
helpful for us to diagnose the issue quickly.

Sincerely,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[Jack]

I may be missing something with regard to how the webrequest is used. What
I did is make the webrequest a global since I go in and out of the sub and
want to maintain the session across these calls. The first request (a
Post), second (a Get) and third (a Post) work fine, but if I try to reenter
and execute the same requests again they time out. I am executing a
"WebRequest 1 = Net.WebRequest. Create(strUrl)" on each of the requests since
they go to different URLs, is that correct? Is there something that I am
just not getting about how this works and how the session is kept active?

Jack
"Walter Wang [MSFT]" <wa****@online. microsoft.comwr ote in message
news:Vy******** ******@TK2MSFTN GXA01.phx.gbl.. .

Hi Jack,

From your post title and first part, your question seems to "how to force
the connection close".

By default, HttpWebRequest. KeepAlive is true. So the connections should be
reused from one request to the next. And I don't think you need to
explicitly close the connection, just dispose the HttpWebRequest object.

Also, note that the server could also be closing the connection after
serving each request. Keep-alive can be set in the http request header,
but
server can decide whether or not to reuse the connection.

Reusing connection is to improve performance. I don't think it's required
to maintain the login credential. As long as you are using the same
HttpWebRequest object, the credential should be used in subsequent
requests.

As your last question about "subsequent posts time out", I think this is
probably because the request size limit. If your server is written in
ASP.NET, the default maximum request size is 4MB. You can change this
limit
in web.config:

<system.web>
<httpRuntime maxRequestLengt h="10240" /<!-- change to 10MB -->

http://msdn2.microsoft.com/en-us/library/e1f13641.aspx

maxRequestLengt h:

Specifies the limit for the input stream buffering threshold, in KB.
This limit can be used to prevent denial of service attacks that are
caused, for example, by users posting large files to the server.

Also, you can use WebClient to do the post:
http://msdn2.microsoft.com/en-us/library/tt0f69eh.aspx

If my assumption is not the case, I think a repro project would be very
helpful for us to diagnose the issue quickly.

Sincerely,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Walter Wang [MSFT]]

Hi Jack,

Although you make the webrequest a global variable, but you are recreating
it on each request by Net.WebRequest. Create(strUrl).

To maintain the session after you first logged on, you need to use a
CookieContainer to store the cookies you obtained after the first request
to logon. For more information, see
http://blogs.vbcity.com/drydo/archiv...9/27/5556.aspx

Hope this helps. Please feel free to post here if anything is unclear.

Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[Jack]

I looked at the code in the link you attached and that is basically what I
am doing for my logon and response. How would I compose my next post
request? Do I use .create(url) and then set .cookiecontaine r = CookieC?

Also, is there a good resource on coding this? I have purchased "MS Visual
Basic 2005: The Language", "101 Visual Basic .NET Applications", "Visual
Studio Tools for Office" and A! Apress's "Programmin g the Web with Visual
Basic .NET"; none of which really seem to take about using the WebRequest
object to access secure web resources inside a VB.NET Windows Application.

Jack

"Walter Wang [MSFT]" <wa****@online. microsoft.comwr ote in message
news:cK******** ******@TK2MSFTN GXA01.phx.gbl.. .

Hi Jack,

Although you make the webrequest a global variable, but you are recreating
it on each request by Net.WebRequest. Create(strUrl).

To maintain the session after you first logged on, you need to use a
CookieContainer to store the cookies you obtained after the first request
to logon. For more information, see
http://blogs.vbcity.com/drydo/archiv...9/27/5556.aspx

Hope this helps. Please feel free to post here if anything is unclear.

Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Walter Wang [MSFT]]

Hi Jack,

Thank you for your update. You are right that you need to pass the
CookieContainer object to your second request.

When using System.Net or Web Services, you might want to receive or send
cookies, perhaps for session state maintenance or in some rate situations
for proxy authentication. CookieContainer is designed to be a store of all
the cookies for one or more requests. To that extent, the CookieContainer
is designed to be a Hashtable of "domain - CookieCollectio n" pairs.

For more information, please refer to following article:

#Cookies, Cookie Collection and CookieContainer
http://blogs.msdn.com/dgorti/archive...16/452347.aspx

And here're some other KB articles related to CookieContainer you may find
useful:

#How to authenticate the Inbox in Exchange Server 2003 with forms-based
authentication enabled by using Visual Basic.NET
http://support.microsoft.com/kb/891748/

#HOW TO: Use CookieContainer to Maintain a State in Web Services Using
Visual Basic.NET
http://support.microsoft.com/kb/820528/

Hope this helps. Please feel free to post here if anything is unclear.
Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.