Download the PHP package amphp/http without Composer
On this page you can find all versions of the php package amphp/http. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package http
amphp/http
AMPHP is a collection of event-driven libraries for PHP designed with fibers and concurrency in mind.
amphp/http
is a collection of basic HTTP primitives which can be shared by servers and clients.
Installation
This package can be installed as a Composer dependency.
This package requires PHP 8.1 or later.
Usage
This package provides basic primitives needed for HTTP clients and servers.
- Status codes
- Cookies
- Headers
Status Codes
HTTP status codes are made human-readable via Amp\Http\HttpStatus
.
It includes a constant for each IANA registered status code.
Additionally, a default reason is available via HttpStatus::getReason($code)
.
Cookies
HTTP cookies are specified by RFC 6265.
This package implements parsers for the set-cookie
and cookie
headers.
It further has a developer friendly API for creating such headers.
Note This library doesn't set standards regarding the cookie encoding. As such, the limitations of RFC 6265 apply to names and values. If you need to set arbitrary values for certain cookies, it's recommended to use an encoding mechanism like URL encoding or Base64.
Set-Cookie
The set-cookie
header is used to create cookies.
Servers send this header in responses and clients parse the headers if a response contains such headers.
Every header contains exactly one header.
Hence, the responsible class is called ResponseCookie
.
Note More information about
set-cookie
can be obtained from the MDN reference or other sources.
ResponseCookie::fromHeader()
accepts a header value and attempts to parse it.
If the parsing succeeds, a ResponseCookie
is returned.
If not, null
is returned.
No exceptions are thrown, because received cookies are always user input and untrusted and malformed headers should be discarded according to the RFC.
Cookie
The cookie
header is used to send cookies from a client to a server.
Clients send this header in requests and servers parse the header if a request contains such a header.
Clients must not send more than one such header.
Hence, the responsible class is called RequestCookie
.
Note More information about
cookie
can be obtained from the MDN reference or other sources.
RequestCookie::fromHeader()
accepts a header value and attempts to parse it.
If the parsing succeeds, an array of RequestCookie
instances is returned.
If not, an empty array is returned.
No exceptions are thrown, because received cookies are always user input and untrusted and malformed headers should be discarded according to the RFC.
Headers
This package provides an HTTP header parser based on RFC 7230. It also provides a corresponding header formatter.
Parsing Headers
Amp\Http\Rfc7230::parseHeaders()
parses raw headers into an array mapping header names to arrays of header values.
Every header line must end with \r\n
, also the last one.
Formatting Headers
Amp\Http\Rfc7230::formatHeaders()
takes an array with the same format as parseHeaders()
returns.
It protects against header injections and other non-compliant header names and values.
Versioning
amphp/http
follows the semver semantic versioning specification like all other amphp
packages.
Note BC breaks that are strictly required for RFC compliance are not considered BC breaks. These include cases like wrong quote handling for cookies, where the RFC isn't too clear.
A lax parser will however not be changed unless it is necessary for security reasons.
Security
If you discover any security related issues, please email [email protected]
instead of using the issue tracker.
License
The MIT License (MIT). Please see LICENSE
for more information.