Libraries tagged by rf

The missing PHP TFTP Client package compliant with RFC 1350

Go to Download

Forked from hiqdev: Registration Data Access Protocol – core objects implemantation package accodring to the RFC 7483

Go to Download

Logger with eight methods for writing logs to the eight RFC 5424 levels (debug, info, notice, warning, error, critical, alert, emergency).

Go to Download

catch all Symfony 3.3 or newer errors and convert it to problem json RFC7807 response

Go to Download

PHP implementation of RFC 4151: The 'tag' URI Scheme

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.44) is used. For example, calling `/info` is the same as calling `/v1.44/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

Email delivery class that provides the basic requirements in order to send RFC compliant emails.

Go to Download

Rough implementation of an RFC1413 (IDENT) client

Go to Download

Simple TOTP (RFC 6238)

Go to Download

A parser for the Accept-Language HTTP header following RFC 2616

Go to Download

PHP TOTP implementation for rfc6238

Go to Download

Email verification using RFCs, Mailgun.

Go to Download

sskaje's BaseXX Encode/Decode class, a PHP implemention of RFC 3548, supports Base16/Base32/Base64 in both LSB and MSB, and another Base32 used by VMware

Go to Download

SocketIO implementation using RFC6455-compliant websockets only. Built on top of Swoole Websocket Server.

Go to Download

Pure-PHP implementation of the OpenPGP Message Format (RFC 4880)

Go to Download