Libraries tagged by base64-encode

PHP Base64 file decoder and encoder

Go to Download

常用数据加密和解密处理方法

Go to Download

file to base64 encode

Go to Download

This class can encode and decode data in base64 in pure PHP. It can take a data string and encode it using the base64 algorithm. The class can also do the opposite, i.e. decode base64 encoded data and return the original data string.

Go to Download

Base64 Encode Decode With Key

Go to Download

Laravel file receive with base64 encode, store it and generate file url. Than you can get the file with the url

Go to Download

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

Go to Download

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

Go to Download

A powerful Laravel package for handling base64 encoded images with automatic resizing, validation, and storage management

Go to Download

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

Go to Download

Lumen validators for base64 encoded files

Go to Download

Missing laravel validation rules for base64 encoded strings and files.

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

Allows to generate URL compliant base64-encoded strings.

Go to Download

Base64 encoder/decoder with URL safe alphabet (base64url).

Go to Download