Libraries tagged by cors
cors/demo
0 Downloads
kas-cor/console-progress-bar
50 Downloads
Console progress bar
corsidrive/test-tools
11 Downloads
corsicanec82/brain-games
30 Downloads
Simple brain games
corsdev/simpleframework-core
10 Downloads
corsdev/simpleframework
4 Downloads
corsair/m360
8 Downloads
M360API PHP Middleware with support to Symfony, and Laravel
cor-kalom/magento2-b2b-disable-customer-registration
11 Downloads
This extension allows you to disable customer registration in your Magento 2.
drlenux/chain
2 Downloads
CoR
xililo/yii2-pdfjs
5 Downloads
Previewer PDF File with PDF.js for Yii2 with CORS unrestricted
viablelabs/multi-oauth2
1541 Downloads
A package that combines oauth2, cors requests and auth on multiple tables
tigrino/tigrino-framework
7 Downloads
A basic framework who you can set like you want, with CORS, Routes, and Auth
spatial/route
33 Downloads
PHP routing which contains Authorization, CORS, nexted routes
shelob9/jp-rest-access
11 Downloads
Sets CORS headers, and allows offest in posts route, with max post per page for WordPress REST API (WP-API).
nodeum-io/nodeum-sdk-php
0 Downloads
The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>