Libraries tagged by php http server

Clase para servir archivos con 'HTTP/1.1 206 Partial Content'

Go to Download

Provides facilities to read table names and table columns from a database using PDO. This package is a fork of https://packagist.org/packages/aura/sqlschema ( https://github.com/auraphp/Aura.SqlSchema ). It adds PHP 8.1+ suport and is also designed to work with Mariadb 10.4+ and above.

Go to Download

Simple, light, minimum TUS server connected with AWS S3. Based on https://github.com/ankitpokhrel/tus-php

Go to Download

Eloquent database models for https://github.com/php-loep/oauth2-server OAuth 2 Server. This package does nothing (mostly) without the OAuth2 Server.

Go to Download

Laravel/Lumen Gearman rpc. Based from https://github.com/mhlavac/gearman

Go to Download

扩展实现了 [bshaffer/oauth2-server-php](https://github.com/bshaffer/oauth2-server-php) 的全部功能，简单易用。

Go to Download

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

Go to Download

Based-on OAuth Consumer And Server Library For PHP at https://code.google.com/p/oauth-php/

Go to Download

Package to check version according to Semantic Versioning 2.0.0 (http://semver.org).

Go to Download

A simple library to serve static image files & documents over HTTP/S via PHP. | © Nick Freear (IET-OU).

Go to Download

Gearman job server workers helper forked from https://github.com/pauloborgesccb/php-gearman

Go to Download

Framework based on https://bref.sh/ for building serverless PHP applications on AWS Lambda

Go to Download

paysafe SDK customize for composer uses and more configuration. for more information please visit https://developer.paysafe.com/en/sdks/server-side/php/introduction/

Go to Download

A brief overview of the API versions: v0: This version is solely for testing and does not interact with the database, nor does it involve any validation. It simply serves mock data. v1: This is the official version of the LtiSaas API, intended for production use. Please be informed that when testing version v0, the HTTP Access-Token header should be set with the value 'dummy'. Also, please note that the API has a limit of 2500 results per response. Additionally, all webservices support both POST and GET requests. However, the POST method is required when uploading files.

Go to Download

# Summary The **NextGenPSD2** *Framework Version 1.3.6* (with errata) offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGenPSD2 Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe and, aligned with the goals of the Euro Retail Payments Board, enables European banking customers to benefit from innovative products and services ('Banking as a Service') by granting TPPs safe and secure (authenticated and authorised) access to their bank accounts and financial data. The possible Approaches are: * Redirect SCA Approach * OAuth SCA Approach * Decoupled SCA Approach * Embedded SCA Approach without SCA method * Embedded SCA Approach with only one SCA method available * Embedded SCA Approach with Selection of a SCA method Not every message defined in this API definition is necessary for all approaches. Furthermore this API definition does not differ between methods which are mandatory, conditional, or optional. Therefore for a particular implementation of a Berlin Group PSD2 compliant API it is only necessary to support a certain subset of the methods defined in this API definition. **Please have a look at the implementation guidelines if you are not sure which message has to be used for the approach you are going to use.** ## Some General Remarks Related to this version of the OpenAPI Specification: * **This API definition is based on the Implementation Guidelines of the Berlin Group PSD2 API.** It is not a replacement in any sense. The main specification is (at the moment) always the Implementation Guidelines of the Berlin Group PSD2 API. * **This API definition contains the REST-API for requests from the PISP to the ASPSP.** * **This API definition contains the messages for all different approaches defined in the Implementation Guidelines.** * According to the OpenAPI-Specification [https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md] "If in is "header" and the name field is "Accept", "Content-Type" or "Authorization", the parameter definition SHALL be ignored." The element "Accept" will not be defined in this file at any place. The elements "Content-Type" and "Authorization" are implicitly defined by the OpenApi tags "content" and "security". * There are several predefined types which might occur in payment initiation messages, but are not used in the standard JSON messages in the Implementation Guidelines. Therefore they are not used in the corresponding messages in this file either. We added them for the convenience of the user. If there is a payment product, which needs these fields, one can easily use the predefined types. But the ASPSP need not to accept them in general. * **We omit the definition of all standard HTTP header elements (mandatory/optional/conditional) except they are mentioned in the Implementation Guidelines.** Therefore the implementer might add these in his own realisation of a PSD2 comlient API in addition to the elements defined in this file. ## General Remarks on Data Types The Berlin Group definition of UTF-8 strings in context of the PSD2 API has to support at least the following characters a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / - ? : ( ) . , ' + Space

Go to Download