Libraries tagged by http-2
amphp/hpack
16531253 Downloads
HTTP/2 HPack implementation.
cat-sys/swoole-etcd
82 Downloads
PHP Etcd v3 Client base on Swoole Http 2.0
dreamcat/swoole_http_2_psr
138 Downloads
Swoole Http 转为 PSR 标准相关对象
raeder/craft-http2-server-push-twig
2769 Downloads
This plugin provides a convenient way to utilize Server Push via a twig filter
divinity76/php-httpreadfile
3 Downloads
readfile() with 304 Not Modified and 206 Partial Content support
shizzen/laravel-http2
123 Downloads
Small Laravel package used to handle HTTP 2 push server
ordereazi/commerce-sdk
5 Downloads
Build a fully custom headless storefront - your own web app, mobile app, or POS - against a single OE Commerce store. Every endpoint below is namespaced under `/api/v1/store/...`. Building admin/back-office tooling instead? See [/docs/admin](/docs/admin). New here? [/guides/store](/guides/store) walks through getting a key, the anonymous cart session, and calling your first endpoints step by step - this page is the field-level reference to come back to afterward. ## Getting Started 1. Click the **Authorize** button at the top of this page. 2. Provide credentials: - **X-Commerce-Key** (always required) - your store's Store Access Key from Backoffice > Settings > Application APIs. `pk_store_...` (publishable) is safe for browser/mobile code; `sk_store_...` (secret) is server-to-server only and is rejected outright if a browser Origin header is present. - **Bearer** (only for endpoints acting on a specific customer - Account, Orders, Wishlists, etc.) - the token from **Auth > register** or **Auth > login**. Once authorized, you can explore and test all available endpoints directly from this interface. ## Anonymous Carts A guest cart is tracked by an `X-Session-Ref` header, not a cookie - the server generates one on your first request and echoes it back on every response after. Keep sending back whatever value you last received. Logging in carries that same cart forward onto the customer's account automatically, with no separate merge step. ## Errors Failures use RFC 9457 Problem Details (`application/problem+json`) with a stable `code` field for programmatic handling, e.g. `store_key_invalid`, `store_key_revoked`, `store_key_scope_denied`, `rate_limited`. A rejected *business* action (e.g. adding fewer than a product's minimum order quantity to the cart) instead comes back as HTTP 200 with `"success": false` and a human-readable `message` - always check `success` in the body, not just the HTTP status code. ## Rate Limits Requests are limited per Store Access Key (200/minute). The credential-stuffing surface (register/login/forgot-password/reset-password) is limited more tightly per caller IP (10 per 5 minutes). A 429 response includes a `Retry-After` header.
duzun/http-socket
1 Downloads
HTTP (<2.0) Requests over Socket - get as close to the socket level as possible
initphp/http-factory
14 Downloads
PSR17 HTTP Factory Library (DEPRECATED — merged into initphp/http:^2.2)
initphp/http-client
8 Downloads
Psr18 HTTP Client Library (DEPRECATED — merged into initphp/http:^2.2)
initphp/curl
52 Downloads
Curl Library (DEPRECATED — use initphp/http:^2.2 for HTTP requests)
r-martins/mautic-plugin-onesignal-web16
3 Downloads
OneSignal Web SDK v16: use include_subscription_ids for web, and mark campaign push as failed when OneSignal returns errors or an empty id in JSON (including HTTP 200).