It sounds like you are looking more for a code review, not a tester. If that is the case, you may get more responses with a different title.

If that is the case, post the code here, within <readmore><code>...</code></readmore> tags. PerlMonks seems to prefer having posts fairly well self contained, in order to allow for the content to be long lived.

That being said, I would probably start your options gathering with Getopt::Long or something similar. Prompting the user is not necessarily a bad thing, but not allowing for automation is (imo). That is all the further I got at this point.

I was actually planning on making this able to take arguments from the command line in a later version - but thanks for pointing out Getopt::Long! That looks like it's a really useful module.

I also took your advice and posted the code here on the post, for everyone to view within the Monastery. Hope that helps!

Some comments on the code:

1. Digest::MD5::md5_hex is imported but not used.

2. $location is initialised via user input but then not used.

3. Line 61 could be simplified to: my $ext = $1;

4. Lines 71 and 72 could be written as a single line: $filename =~ s{.*/(.*)$}{$1};

5. The next statements on lines 76 and 94 are redundant, as each occurs immediately before the loop iterates anyway.

6. In addition, on line 94 the or clause does nothing. next can’t “fail”, and it doesn’t return a value.

7. Lines 101 to 105 could be rewritten as a single line: print $error eq '' ? "No errors.\n" : "\nErrors: $error";

Hope that helps,

In order:

1. You're right! Digest::MD5::md5_hex was used previously to check the md5 hash of the file. I will remove it now that it is no longer used.
2. Whoa, that's a bit of a big error on my part. I guess I edited the use of $location out, but that's not how it's supposed to be. Thanks for catching that.
3. Good point. I'm not very well versed on the intricacies of regular expressions, thanks for the tip.
4. Alright, thanks for the help there, once again regular expressions aren't something I'm used to using much of; usually just simple substitution or word-matching regex's.
5. Good catch, they will be removed.
6. Kind of a newby error to make, on my part. I was trying to simply make sure that many of the possible errors were found and reported to the user, and I didn't take the time to figure out if next even CAN have an error. I'll remove the or statement.
7. Awesome, thanks for that tip :)

That was a lot of help, I'll be sure to tweak the code up using your help! Thanks!

Some minor suggestions:

1. In GetFileSize, change this:

           if ($res->is_success) {
              my $headers = $res->headers;
              return $headers;
           }else{
              $flag = 1;
              $error .= "Error retrieving file information at $url ";
           }
           return 0;
   [download]

   To this:

           return $res->headers    if $res->is_success;
   
           $flag   = 1;
           $error .= "Error ...";
           return 0;
   [download]

2. Within your for loop, change this:

      if(exists($extens{$ext})){
   [download]

   To this, and remove one level of indentation.

      next unless exists $extens{$ext};
   [download]

3. Change delimiters rather than escaping. And in this example the global modifier isn't necessary.

      #if($newurl !~ /http::\/\/$/ig){
       if($newurl !~ m#http:://$#i){
   [download]

4. $skips -= 1; vs. $skips--;?
5. Change this:

   print"\n\n\n$filename at $newurl\n";
   print "File size: ".$header->content_length." bytes\n" unless $flag==1
   +;
   print "Last modified: ".localtime($header->last_modified)."\n" unless 
   +$flag==1;
   [download]

   To this:

   print "\n\n\n$filename at $newurl\n",
   printf("File size: %d bytes\nLast modified: %s\n", $header->content_le
   +ngth, localtime($header->last_modified)) unless $flag == 1;
   [download]

6. Spelling and grammar...

      #print"\nExtensions to download (seperated by comma's): ";
       print"\nExtensions to download (separated by commas): ";
   [download]

Great suggestions all - will definitely make the code more elegant. I haven't coded in Perl for a while, I guess I've forgotten how to make beautiful code :) thanks for the help!

If you need this for your job, then why not just use curl?

curl has more features than you can shake a stick at, and just works -- no coding required :)

Because at the time, due to Windows 8 sucking, curl wasn't working - so I made this, found out Windows 8 was causing everything not to work, transferred the program to a different computer that runs a different OS, and basically now we have our own tool already, so why not use it? :)

All your points are good, I'll look into LWP callbacks so I can avoid HEAD requests - the mixing of decoded_content and content_file was due to me misunderstanding what decoded_content did. Can you elaborate what it does a little bit, for me?

Documentation for decoded_content: http://search.cpan.org/perldoc?HTTP%3A%3AMessage Note that there is no content at all, as file downloaded using content_file option.