in reply to Using WWW::Mechanize::Chrome to log into content restricted by apache

Does this actually work if you do it manually with Chrome? Apparently:

Use of the format "user:password" in the userinfo field is deprecated. Applications should not render as clear text any data after the first colon (":") character found within a userinfo subcomponent unless the data after the colon is the empty string (indicating no password). Applications may choose to ignore or reject such data when it is received as part of a reference and should reject the storage of such data in unencrypted form. The passing of authentication information in clear text has proven to b +e a security risk in almost every case where it has been used.

Update: Also this.

  • Comment on Re: Using WWW::Mechanize::Chrome to log into content restricted by apache
  • Download Code

Replies are listed 'Best First'.
Re^2: Using WWW::Mechanize::Chrome to log into content restricted by apache
by nysus (Parson) on Apr 06, 2019 at 20:30 UTC

    I'm using Chromium. Yeah it doesn't work in Chromium if I enter that URL directly into the address bar. But what's weird is if I try with WMC and then refresh the browser manually, it does, in fact log me in. I can't even do that if I manually type in the url.

    $PM = "Perl Monk's";
    $MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate Priest Vicar";
    $nysus = $PM . ' ' . $MCF;
    Click here if you love Perl Monks