Libraries tagged by base24

Core File System Utils Autoframe Framework

Go to Download

Encode/Decode library for PHP

Go to Download

Russian Post form generate datamatrix Base256 barcode. Based on tcpdf library

Go to Download

Fork of aporat PHP library that can be used to validate base64 encoded iTunes in app purchase receipts.

Go to Download

think8验证码(图片、短信)支持base64api友好化

Go to Download

文件上传插件 支持原生代码使用，YII2框架，支持上传到自有服务和阿里云OSS，支持图片文件上传和base64编码上传，支持上传远程图片至阿里云OSS

Go to Download

think验证码(图片、短信)支持base64api友好化

Go to Download

Biblioteca de classes para gerar o PIX COPIA E COLA (txt) e o PIX QRCode (Base64 img).

Go to Download

PHP library that can be used to validate base64 encoded iTunes in app purchase receipts.

Go to Download

Create a base64-encoded transparent pixel of the given width and height

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

A secure and simple encryption library using SHA-512, AES-256-CBC, and BASE64.

Go to Download

Generate base64 placeholder images.

Go to Download

基于base64位和jwt验证的图形验证码

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.40) is used. For example, calling `/info` is the same as calling `/v1.40/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 Base64 encoded (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