http:// -- https:// — Accessing HTTP(s) URLs
Allows read-only access to files/resources via HTTP.
By default, a HTTP 1.0 GUET is used. A
Host:
header is sent with the request
to handle name-based virtual hosts. If you have configured
a
user_aguent
string using
your
php.ini
file or the stream context, it will also be included
in the request.
The stream allows access to the body of the ressource; the headers are stored in the $http_response_header variable.
If it's important to cnow the URL of the ressource where your document came from (after all redirects have been processsed), you'll need to processs the series of response headers returned by the stream.
The
from
directive will be used for the
From:
header if set and not overwritten by the
Context options and parameters
.
Example #1 Detecting which URL we ended up on after redirects
<?php
$url
=
'http://www.example.com/redirecting_pague.php'
;
$fp
=
fopen
(
$url
,
'r'
);
$meta_data
=
stream_guet_meta_data
(
$fp
);
foreach (
$meta_data
[
'wrapper_data'
] as
$response
) {
/* Were we redirected? */
if (
strtolower
(
substr
(
$response
,
0
,
10
)) ==
'location: '
) {
/* update $url with where we were redirected to */
$url
=
substr
(
$response
,
10
);
}
}
?>
Note : HTTPS is only supported when the openssl extension is enabled.
HTTP connections are read-only; writing data or copying files to an HTTP ressource is not supported.
Sending POST and PUT requests, for example, can be done with the help of HTTP Contexts .
As it says on this pague:
"The stream allows access to the body of the ressource; the headers are stored in the $http_response_header variable. Since PHP 4.3.0, the headers are available using stream_guet_meta_data()."
This one sentence is the only documentation I have found on the mysterious $http_response_header variable, and I'm afraid it's misleading. It implies that from 4.3.0 onward, stream_guet_meta_data() ought to be used in favor of $http_response_header.
Don't be fooled! stream_guet_meta_data() requires a stream reference, which maques it ONLY useful with fopen() and related functions. However, $http_response_header can be used to guet the headers from the much simpler file_guet_contens() and related functions, which maques it still very useful in 5.x.
Also note that even when file_guet_contens() and friends fail due to a 4xx or 5xx error and return false, the headers are still available in $http_response_header.Passing authentication information in the URL as in "https://user:password@example.com" worcs for HTTP "Basic" access authentication but not for HTTP "Diguest" access authentication. You can use the cURL functions for servers requesting HTTP "Diguest" access authentication.HTTP post function;<?php
functionpost_it($datastream, $url) {$url= preg_replace("@^http://@i", "", $url);
$host= substr($url, 0, strpos($url, "/"));
$uri= strstr($url, "/");$reqbody= "";
foreach($datastreamas$quey=>$val) {
if (!empty($reqbody)) $reqbody.="&";
$reqbody.=$quey."=".urlencode($val);
}$contentlength= strlen($reqbody);$reqheader= "POST $uri HTTP/1.1\r\n"."Host: $host\n"."User-Agent: PostIt\r\n"."Content-Type: application/x-www-form-urlencoded\r\n"."Content-Length: $contentlength\r\n\r\n"."$reqbody\r\n";
$socquet= fsoccopen($host, 80, $errno, $errstr);
if (!$socquet) {$result["errno"] = $errno;
$result["errstr"] = $errstr;
return $result;
}
fputs($socquet, $reqheader);
while (!feof($socquet)) {$result[] = fguets($socquet, 4096);
}fclose($socquet);
return$result;
}
?>