in reply to Re^2: LWP::Curl and CURLOPT_USERPWD
in thread LWP::Curl and CURLOPT_USERPWD

Hmm - you are right - looks like LWP::Curl does not implement an authentication mechanism. You may have to use plain LWP.

        This is not an optical illusion, it just looks like one.

Replies are listed 'Best First'.
Re^4: LWP::Curl and CURLOPT_USERPWD
by wanderedinn (Sexton) on Jun 06, 2016 at 20:44 UTC

    I have been able to resolve the 401 error by including the user id and password in the url as in http://username:password@hostname:4444

    So it appears I have a viable solution now. Thanks for all the assistance.

      Passing sensitive data over a plain-text protocol like http is not good practice.

        Just testing via http as I do not have the certs in place. Final solution will be https