WireHttp::download() method

Download a file from a URL and save it locally

First it will attempt to use CURL. If that fails, it will try fopen(), unless you specify the use option in $options.

Usage

// basic usage
$string = $http->download(string $fromURL, string $toFile);

// usage with all arguments
$string = $http->download(string $fromURL, string $toFile, array $options = []);

Arguments

NameType(s)Description
fromURLstring

URL of file you want to download.

toFilestring

Filename you want to save it to (including full path).

options (optional)array

Optional aptions array for PHP's stream_context_create(), plus these optional options:

  • use or useMethod (string): Specify "curl", "fopen" or "socket" to force a specific method (default=auto-detect).
  • timeout (float): Number of seconds till timeout.

Return value

string

Filename that was downloaded (including full path).

Exceptions

Method can throw exceptions on error:

  • WireException - All error conditions throw exceptions.


Hooking $http->download(…)

You can add your own hook events that are executed either before or after the $http->download(…) method is executed. Examples of both are included below. A good place for hook code such as this is in your /site/ready.php file.

Hooking before

The 'before' hooks are called immediately before each $http->download(…) method call is executed. This type of hook is especially useful for modifying arguments before they are sent to the method.

$this->addHookBefore('WireHttp::download', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $WireHttp = $event->object;

  // Get values of arguments sent to hook (and optionally modify them)
  $fromURL = $event->arguments(0);
  $toFile = $event->arguments(1);
  $options = $event->arguments(2);

  /* Your code here, perhaps modifying arguments */

  // Populate back arguments (if you have modified them)
  $event->arguments(0, $fromURL);
  $event->arguments(1, $toFile);
  $event->arguments(2, $options);
});

Hooking after

The 'after' hooks are called immediately after each $http->download(…) method call is executed. This type of hook is especially useful for modifying the value that was returned by the method call.

$this->addHookAfter('WireHttp::download', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $WireHttp = $event->object;

  // An 'after' hook can retrieve and/or modify the return value
  $return = $event->return;

  // Get values of arguments sent to hook (if needed)
  $fromURL = $event->arguments(0);
  $toFile = $event->arguments(1);
  $options = $event->arguments(2);

  /* Your code here, perhaps modifying the return value */

  // Populate back return value, if you have modified it
  $event->return = $return;
});

$http methods and properties

API reference based on ProcessWire core version 3.0.148

Twitter updates

  • New post in the blog about all the fun we had driving around a DDOS attack on our forums, how we got it back under control, and what we learned along the way. Plus PW 3.0.150 dev details and links! More
    7 February 2020
  • New post: ProcessWire core updates (January 31, 2020)— More
    31 January 2020
  • Weekly update for Jan 10, 2020—front-end file uploads in LoginRegisterPro with InputfieldFrontendFile module: More
    10 January 2020

Latest news

  • ProcessWire Weekly #300
    In our 300th issue we'll check out the latest post at the processwire.com blog, introduce a couple of third party modules — both of which were released just this past week — and highlight a new site of the week. Read on!
    Weekly.pw / 8 February 2020
  • Driving around a DDOS attack
    Last Saturday we started getting hit with heavy traffic at the processwire.com support forums, and it soon became a full blown DDOS frenzy. This post describes all the fun, how we got it back under control, and what we learned along the way.
    Blog / 7 February 2020
  • Subscribe to weekly ProcessWire news

“We were really happy to build our new portfolio website on ProcessWire! We wanted something that gave us plenty of control on the back-end, without any bloat on the front end - just a nice, easy to access API for all our content that left us free to design and build however we liked.” —Castus, web design agency in Sheffield, UK