in reply to Re: LWP and Digest Authentication
in thread LWP and Digest Authentication

What exactly do you think those links are meant to tell me?

  1. The grep references digest, but tells me nothing I do not already know.
  2. The second is a test script testing authentication...

    But, as I pointed out above, it hardcodes the realm rather than deriving it from the 401 header.

    No help there then.

  3. The third is a test script checking an MD5 content header?

I don't know who you are (though I could probably take a good guess), but quite what you thought the point of your contribution was, I cannot fathom from your terse response.

Perhaps that's why your post was so terse; you didn't know what you were trying to say?


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Replies are listed 'Best First'.
Re^3: LWP and Digest Authentication
by Anonymous Monk on Feb 11, 2009 at 03:58 UTC
    They were suggestions for you to look at, sorry. I don't see where it hardcodes the realm. I get
    1..2 test:http://jigsaw.w3.org/HTTP/Digest/: => foo/bar test:http://jigsaw.w3.org/HTTP/Digest/: => / test:http://jigsaw.w3.org/HTTP/Digest/: => guest/ test:http://jigsaw.w3.org/HTTP/Digest/: => guest/guest ok 1 ok 2
    test doesn't appear anywhere in the code and the docs for get_basic_credentials say The arguments passed in is the $realm provided by the server, the $uri requested and a boolean flag to indicate if this is authentication against a proxy server. so isn't this what you want?