Libraries tagged by https server

nabu-3 Provider to add PHP Server support

Go to Download

nabu-3 Provider to add Apache Server support

Go to Download

A HTTP(S) library for LiteRT.

Go to Download

An HTTP proxy server based on swoole

Go to Download

Event-driven, streaming HTTP client and server implementation for ReactPHP

Go to Download

PHP SDK for Synapse server (https://matrix.org/docs/api/client-server)

Go to Download

Hello World PHP app for Metaport Server: https://metaport.sh

Go to Download

A Laravel package to easily configure and manage proxy servers, supporting HTTP, HTTPS, SOCKS4, and SOCKS5 proxies with authentication, logging, and customizable routing rules.

Go to Download

Forward your HTTP/HTTPS requests to another server.

Go to Download

imi 框架的 UDP Server 项目。https://imiphp.com

Go to Download

Implementation of Event Source API (Server-Sent Events https://www.w3.org/TR/eventsource)

Go to Download

OAuth2 Server for Laravel, using https://github.com/bshaffer/oauth2-server-php

Go to Download

Using Server side validation based on https://github.com/sirprize/postal-code-validator

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

Small set of tools to help work with JSend specifications (see https://labs.omniti.com/labs/jsend). Package is done for yii2 framework and yii2-oauth2-server. Package was build to simplify bilding response for API using this tools.

Go to Download