Do you want it to be silent for the redirection? Use a simple_request instead of request. 

my $ua = LWP::UserAgent->new;
my $uri = shift @ARGV;
my $headreq = HTTP::Request->new(HEAD => $uri);        
my $headres = $ua->simple_request($headreq);   # <----
my $statuscode = $headres->code();        
print "Status 401 at $uri\n" if $statuscode == 401;

[download]

Or do you wish for it to display the uri to which you were redirected? Access it through the Request that produced the Response. 

my $ua = LWP::UserAgent->new;
my $uri = shift @ARGV;
my $headreq = HTTP::Request->new(HEAD => $uri);        
my $headres = $ua->request($headreq);        
my $statuscode = $headres->code();        
if ($statuscode == 401) {
   my $final_uri = $headres->request()->uri();   # <----
   print "Status 401 at $final_uri\n" 
}

[download]

In reply to Re: HTTP status codes by ikegami
in thread HTTP status codes by memwaster

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.