HTTP and HTTPS
PHP 4, PHP 5, PHP 6. https:// since PHP 4.3.0
- http://example.com
- http://example.com/file.php?var1=val1&var2=val2
- http://user:password@example.com
- https://example.com
- https://example.com/file.php?var1=val1&var2=val2
- https://user:password@example.com
Allows read-only access to files/resources via HTTP 1.0,
using the HTTP GET method. A Host: header is sent with the request
to handle name-based virtual hosts. If you have configured
a user_agent string using
your ini file or the stream context, it will also be included
in the request.
ВниманиеПри использовании SSL,
Microsoft IIS нарушает протокол, закрывая соединение без отправки
индикатора close_notify. PHP сообщит об этом как о "SSL: Fatal Protocol Error"
в тот момент, когда вы достигнете конца данных. Чтобы обойти это, вы должны
установить error_reporting на
уровень, исключающий E_WARNING.
PHP версий 4.3.7 и старше умеет определять, что на стороне сервера находится
проблемный IIS и не выводит предупреждение.
Если вы используете fsockopen() для создания ssl:// сокета,
вы сами отвечаете за определение и подавление этого предупреждения.
Redirects have been supported since PHP 4.0.5; if you are using
an earlier version you will need to include trailing slashes in
your URLs. If it's important to know the URL of the resource where
your document came from (after all redirects have been processed),
you'll need to process the series of response headers returned by the
stream.
The stream allows access to the body of
the resource; the headers are stored in the
$http_response_header variable.
Since PHP 4.3.0, the headers are available using
stream_get_meta_data().
HTTP connections are read-only; you cannot write data or copy
files to an HTTP resource.
Замечание:
HTTPS is supported starting from PHP 4.3.0, if you
have compiled in support for OpenSSL.
Wrapper Summary
Attribute |
Supported |
Restricted by allow_url_fopen |
Yes |
Allows Reading |
Yes |
Allows Writing |
No |
Allows Appending |
No |
Allows Simultaneous Reading and Writing |
N/A |
Supports stat() |
No |
Supports unlink() |
No |
Supports rename() |
No |
Supports mkdir() |
No |
Supports rmdir() |
No |
Custom headers may be sent with an HTTP request prior to
version 5 by taking advantage of a side-effect in the
handling of the user_agent INI setting.
Set user_agent to any valid string
(such as the default PHP/version setting)
followed by a carriage-return/line-feed pair and any
additional headers.
This method works in PHP 4 and all later versions.
Пример #1 Sending custom headers with an HTTP request
<?php
ini_set('user_agent', "PHP\r\nX-MyCustomHeader: Foo");
$fp = fopen('http://www.example.com/index.php', 'r');
?>
Results in the following request being sent:
GET /index.php HTTP/1.0
Host: www.example.com
User-Agent: PHP
X-MyCustomHeader: Foo