Digest Authentification

[rgould8 at aol.com]

Ok, I think I have just enough brain cells left to figure out 80% of the Digest Authentification in Revolution - - - I just need a little nudge over a few small potholes.

A huge thanks to Yennie, who probably saved me 3 weeks of work trying to decypher the rfc for Digest Authentification.

The first question I have is this:  what is the Revolution command to retrieve the header information of the html page that comes back?  For instance, when I make my initial call to the device, putting URL:  http://192.168.1.1/isp/cpe_info.xml, I get a web-page that says:

Page not available.  Protected Object.

This is exactly what I'd expect to see, but what I really need is the header info that comes along with that page.  The header info should look something like this:

HTTP/1.1
401
Unauthorized
Digest realm="DSLUnit BEFDSR41W", nonce="8ce0cfdc62f8bdae849610f521a3538f", qop=auth

I see Revolution commands to SET headers, but I'm just not seeing the command to GET the header.

And then, if I'm reading the spec correctly, I'm supposed to reply with a new header which looks like this:

GET /isp/cpe_info.xml HTTP/1.1
DSL RouterUnit
192.168.1.1
Keep-Alive
Digest username="admin", realm="DSLUnit BEFDSR41W", qop="auth", algorithm="MD5", uri="/isp/cpe_info.xml", nonce="8ce0cfdc62f8bdae849610f521a3538f", nc=00000001, cnonce-"f0f06d6390b9a311f9446d8a30fb2253", response="03b79aca10595873a3bf08f6de0b34e2"


>From reading Yennie's code, I think I see how to parse the headers and MD5 the results to get a new reponse-code.  I could use a little advice on how to get the headers in Revolution, however.  Also, if anyone sees anything odd about the formatting of what I've shown above, please let me know - - - this is my first time trying such things.

- Rob