469,648 Members | 1,190 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,648 developers. It's quick & easy.

Any way to maintain a digest-authenticated session in .NET?

I must (as a client application) connect via HTTP, authenticate using
DIGEST authentication, and then make subsequent HTTP requests.

The Problem:

If I use System.Net.WebClient or System.Net.HttpWebRequest, my initial
HTTP request is met with a:

HTTP/1.1 401 Unauthorized xxx
Set-Cookie: ARPT=ZYQ123; path=/
Date: Sat, 26 Mar 2005 02:43:44 GMT
Content-Length: 0
Content-Type: text/html
Cache-Control: private
WWW-Authenticate: Digest realm="xyz",
nonce="31313131383035303234343234201d4e1fddab881c9 6a4ab8f32f64eaad9",
opaque="6e6f742075736564"

which .NET responds to CORRECTLY by doing a DIGEST authentication.

The problem is that subsequent requests through the .NET framework
using either System.Net.WebClient or System.Net.HttpWebRequest do NOT
contain DIGEST authentication headers, as they should for an
AUTHENTICATED SESSION. Packet traces confirm this.

How can I get .NET to maintain the session, and not treat subsequent
HTTP requests as if I am "starting a session from scratch?" I hope
that Microsoft will not force me to develop my own digest
authentication routines, and have to manually compute and send
authentication headers with each HTTP request.

Thanks in advance!

Nov 19 '05 #1
0 1189

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Jp Calderone | last post: by
3 posts views Thread by John Reese | last post: by
2 posts views Thread by john | last post: by
1 post views Thread by trapeze.jsg | last post: by
2 posts views Thread by trapeze.jsg | last post: by
1 post views Thread by Raghu | last post: by
reply views Thread by Wayne Carlaw | last post: by
1 post views Thread by Jerry LeVan | last post: by
1 post views Thread by Thomas Liesner | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.