I'm having difficulty with PHP's **`file_get_contents` hanging for 60s** when accessing certain resources over https.

I'm not sure whether it's a client or server end issue.

On the client
-------------

Working on the command line:

```
$ URL="https://example.com/some/path"
$ wget "$URL" -O /dev/null -q # takes a few milliseconds
$ curl "$URL" >/dev/null      # takes a few milliseconds
$ php -r 'file_get_contents("'"$URL"'")' # takes 61s!

```

On the server
-------------

An line is written to the Apache (2.4) access log for the correct SSL vhost **immediately**, with a 200 (success) response. This is confusing a confusing timeline:

* 0s php's file\_get\_contents triggered on client
* 0.2s server's apache access log logs a successful (200).
* ???who knows what is going on here???
* 60.2s client receives the file.

Tested from Ubuntu 14.04 and Debian 8 clients. The resources in question are all on Debian 8 servers running Apache 2.4 with ITK worker and PHP 5.6. I've tried it with the firewall turned off (default ACCEPT policy), so it's not that. Nb. the servers have IPv6 disabled, which could be related as I've noticed timeouts like this when something tries IPv6 first. But the hosts being accessed do not have AAAA records, and the apache logs show that (a) the SSL was established Ok and that (b) the request was valid and received.