++ed by:

6 PAUSE users
4 non-PAUSE users.

Jos Boumans


File::Fetch -- A generic file fetching mechanism


    use File::Fetch;

    ### build a File::Fetch object ###
    my $ff = File::Fetch->new(uri => 'http://some.where.com/dir/a.txt');

    ### fetch the uri to cwd() ###
    my $where = $ff->fetch() or die $ff->error;

    ### fetch the uri to /tmp ###
    my $where = $ff->fetch( to => '/tmp' );

    ### parsed bits from the uri ###


File::Fetch is a generic file fetching mechanism.

It allows you to fetch any file pointed to by a ftp, http, file, or rsync uri by a number of different means.

See the HOW IT WORKS section further down for details.


$ff = File::Fetch->new( uri => 'http://some.where.com/dir/file.txt' );

Parses the uri and creates a corresponding File::Fetch::Item object, that is ready to be fetched and returns it.

Returns false on failure.

$ff->fetch( [to => /my/output/dir/] )

Fetches the file you requested. By default it writes to cwd(), but you can override that by specifying the to argument.

Returns the full path to the downloaded file on success, and false on failure.


A File::Fetch object has the following accessors


The uri you passed to the constructor


The scheme from the uri (like 'file', 'http', etc)


The hostname in the uri, will be empty for a 'file' scheme.


The path from the uri, will be at least a single '/'.


The name of the remote file. Will be used as the name for the local file as well.


Returns the last encountered error as string. Pass it a true value to get the Carp::longmess() output instead.


File::Fetch is able to fetch a variety of uris, by using several external programs and modules.

Below is a mapping of what utilities will be used in what order for what schemes, if available:

    file    => LWP, file
    http    => LWP, wget, curl, lynx
    ftp     => LWP, Net::FTP, wget, curl, ncftp, ftp
    rsync   => rsync

If you'd like to disable the use of one or more of these utilities and/or modules, see the $BLACKLIST variable further down.

If a utility or module isn't available, it will be marked in a cache (see the $METHOD_FAIL variable further down), so it will not be tried again. The fetch method will only fail when all options are exhausted, and it was not able to retrieve the file.

A special note about fetching files from an ftp uri:

By default, all ftp connections are done in passive mode. To change that, see the $FTP_PASSIVE variable further down.

Furthermore, ftp uris only support anonymous connections, so no named user/password pair can be passed along.

/bin/ftp is blacklisted by default; see the $BLACKLIST variable further down.


The behaviour of File::Fetch can be altered by changing the following global variables:


This is the email address that will be sent as your anonymous ftp password.

Default is File-Fetch@example.com.


This is the useragent as LWP will report it.

Default is File::Fetch/$VERSION.


This variable controls whether the environment variable FTP_PASSIVE and any passive switches to commandline tools will be set to true.

Default value is 1.

Note: When $FTP_PASSIVE is true, ncftp will not be used to fetch files, since passive mode can only be set interactively for this binary


When set, controls the network timeout (counted in seconds).

Default value is 0.


This variable controls whether errors encountered internally by File::Fetch should be carp'd or not.

Set to false to silence warnings. Inspect the output of the error() method manually to see what went wrong.

Defaults to true.


This enables debugging output when calling commandline utilities to fetch files. This also enables Carp::longmess errors, instead of the regular carp errors.

Good for tracking down why things don't work with your particular setup.

Default is 0.


This is an array ref holding blacklisted modules/utilities for fetching files with.

To disallow the use of, for example, LWP and Net::FTP, you could set $File::Fetch::BLACKLIST to:

    $File::Fetch::BLACKLIST = [qw|lwp netftp|]

The default blacklist is [qw|ftp|], as /bin/ftp is rather unreliable.

See the note on MAPPING below.


This is a hashref registering what modules/utilities were known to fail for fetching files (mostly because they weren't installed).

You can reset this cache by assigning an empty hashref to it, or individually remove keys.

See the note on MAPPING below.


Here's a quick mapping for the utilities/modules, and their names for the $BLACKLIST, $METHOD_FAIL and other internal functions.

    LWP         => lwp
    Net::FTP    => netftp
    wget        => wget
    lynx        => lynx
    ncftp       => ncftp
    ftp         => ftp
    curl        => curl
    rsync       => rsync


So how do I use a proxy with File::Fetch?

File::Fetch currently only supports proxies with LWP::UserAgent. You will need to set your environment variables accordingly. For example, to use an ftp proxy:

    $ENV{ftp_proxy} = 'foo.com';

Refer to the LWP::UserAgent manpage for more details.


Implement $PREFER_BIN

To indicate to rather use commandline tools than modules


This module by Jos Boumans <kane@cpan.org>.


This module is copyright (c) 2003 Jos Boumans <kane@cpan.org>. All rights reserved.

This library is free software; you may redistribute and/or modify it under the same terms as Perl itself.

1 POD Error

The following errors were encountered while parsing the POD:

Around line 873:

You forgot a '=back' before '=head1'