Libraries tagged by cross-domain

hprose/hprose

2002 Favers
222041 Downloads

It is a modern, lightweight, cross-language, cross-platform, object-oriented, high performance, remote dynamic communication middleware. It is not only easy to use, but powerful. You just need a little time to learn, then you can use it to easily construct cross language cross platform distributed application system.

Go to Download


tmilos/scim-filter-parser

12 Favers
1829007 Downloads

System for Cross-domain Identity Management SCIM AST filter parser PHP library

Go to Download


wapplersystems/multisite-belogin

10 Favers
37183 Downloads

Cross site/domain backend login for TYPO3. It allows backend users to work in the frontend across domains.

Go to Download


cloudstek/scim-filter-parser

8 Favers
948433 Downloads

Parser for the SCIM (IETF RFC 7644, System for Cross-domain Identity Management) filter syntax.

Go to Download


blueimp/jquery-file-upload

29 Favers
1526041 Downloads

File Upload widget for jQuery.

Go to Download


hprose/hprose-swoole

179 Favers
29261 Downloads

Hprose asynchronous client & standalone server based on swoole

Go to Download


tiimepdp/cdar

0 Favers
17727 Downloads

CDAR PHP - Cross Domain Acknowledgement and Response Library

Go to Download


hprose/hprose-yii

35 Favers
7224 Downloads

Hprose Server for Yii 2

Go to Download


paypaplane/svix-client

0 Favers
24196 Downloads

Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.

Go to Download


vanthink/hprose-swoole-fork

1 Favers
2115 Downloads

Hprose asynchronous client & standalone server based on swoole

Go to Download


htmldriven/cors-proxy

42 Favers
297 Downloads

A simple proxy service for performing cross-domain AJAX requests.

Go to Download


bunkerdb/jquery-file-upload

1 Favers
14958 Downloads

File Upload server-side for jQuery.

Go to Download


nawasara/search

0 Favers
90 Downloads

Cross-domain search orchestrator for the Nawasara command palette (⌘K). Discovers per-package search providers and aggregates results behind one permission-aware endpoint.

Go to Download


jeffersongoncalves/laravel-security-headers

2 Favers
48 Downloads

This Laravel package stamps a configurable set of baseline security headers (X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, Content-Security-Policy, Cross-Origin-Opener-Policy, X-Permitted-Cross-Domain-Policies and HSTS) onto your HTTP responses via a single middleware. Every header value and the full CSP directive map are driven by config, so you can tune or disable each one without touching code.

Go to Download


basilicom/pimcore-fixtures

1 Favers
582 Downloads

Export Pimcore content to version-controlled YAML and load it into any environment. Follows cross-domain references automatically — objects, documents, assets, and system config in one command.

Go to Download


Next >>