Libraries tagged by base64
fxmonster/validation
237 Downloads
Additional Validator Functions for the Laravel Framework
dentmate/rajahan
23 Downloads
PHP package for encryption/decryption using AES algorithm compatible with CryptoJS
base64/images-converter
128 Downloads
convert image to base64,convert base64 to image
autoframe/components-filesystem
184 Downloads
Core File System Utils Autoframe Framework
asimlqt/encode-decode
72 Downloads
Encode/Decode library for PHP
nielpe87/parsing
19 Downloads
A basic Base64Url and JSON encoding/decoding implementation
cmmia/encrypt
43 Downloads
常用数据加密和解密处理方法
zaboday/store-receipt-validator
54 Downloads
Fork of aporat PHP library that can be used to validate base64 encoded iTunes in app purchase receipts.
yuanmeng/thinkphp8-captcha
12 Downloads
think8验证码(图片、短信)支持base64api友好化
xing.chen/upload
75 Downloads
文件上传插件 支持原生代码使用,YII2框架,支持上传到自有服务和阿里云OSS,支持图片文件上传和base64编码上传,支持上传远程图片至阿里云OSS
wybwsk/thinkphp-captcha
4 Downloads
think验证码(图片、短信)支持base64api友好化
wilbispaulo/php-api-pix
3 Downloads
Biblioteca de classes para gerar o PIX COPIA E COLA (txt) e o PIX QRCode (Base64 img).
vulehd/store-receipt-validator
16 Downloads
PHP library that can be used to validate base64 encoded iTunes in app purchase receipts.
tslol/docker-api-php
2 Downloads
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..." } ```
tibemolde/placeholder-pixel
37 Downloads
Create a base64-encoded transparent pixel of the given width and height