Libraries tagged by headers
marcnewton/laravel-alsl
1035 Downloads
Detects a users language preferences in the Accept-Language request header, from the order of their language preference; an attempt to find and set a matching locale available in Laravel's resources/lang directory.
manish-pareek/laravel-cors
11059 Downloads
Adds CORS (Cross-Origin Resource Sharing) headers support in your Laravel application
machatschek/laravel-server-timing
44782 Downloads
Add Server-Timing header information from within your Laravel apps.
lwplugins/lw-firewall
896 Downloads
Lightweight firewall — rate-limits endpoints, blocks bots, bans repeat offenders, and adds security headers.
los/response-time
66755 Downloads
PHP middleware to add a Response Time header
lolli/peak-memory
8392 Downloads
TYPO3 HTTP memory usage - TYPO3 middleware adding memory_get_peak_usage() as HTTP header
leadtech/http-commons
28218 Downloads
A zero dependency set of definitions to help work with headers and status codes.
laramint/laravel-security-scanner
5039 Downloads
Laravel-aware security rules for php-security-scanner. Detects Laravel SQL injection (DB::raw, whereRaw), mass assignment, debug/dd leaks, unsafe validators, CSRF bypass, insecure cookies, env exposure, Blade raw echo, open redirect, Http SSRF, Storage/File path traversal, file-upload validation gaps, Auth/Crypt/Artisan/Process/Config injection, view-name injection, session fixation, and Mail header injection.
laminas-api-tools/api-tools-http-cache
86012 Downloads
Laminas Module providing http cache headers support
kyzegs/guzzle-rate-limit-middleware
5912 Downloads
A configurable Guzzle middleware for rate limiting HTTP requests based on response headers
kudashevs/accept-language
9766 Downloads
An Accept-Language HTTP header parser.
kronos/csp
215028 Downloads
A Content-Security-Policy header builder
konfig/snaptrade-php-sdk
26074 Downloads
Connect brokerage accounts to your app for live positions and trading. ## Rate limiting Two limits apply to requests signed with your `clientId`. The stricter one wins, and exceeding either returns `429 Too Many Requests`. - **Customer-level** — 250 requests/minute by default, scoped to your `clientId` and applied across all endpoints. Reported in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. - **Account-level** — 10 requests/minute per account, scoped to (`clientId`, `accountId`). All covered operations for one account draw on the same bucket — reading balances and reading positions share it — and enforcement does not depend on the HTTP method, so updating an account consumes the same bucket as reading it. Only enforced for Personal users, and only for integrations it has been rolled out to — it is not yet in force for every Personal integration. It also does not apply on every operation that documents a 429 below. Where it applies it is reported in `X-RateLimit-Account-Limit`, `X-RateLimit-Account-Remaining` and `X-RateLimit-Account-Reset`. Do not read the absence of those headers as proof the limit is off — some configurations omit the rate limit headers while still enforcing the limit, so header absence tells you nothing about your allowance. On a 429, `X-RateLimit-Remaining: 0` means you hit the customer-level limit and `X-RateLimit-Account-Remaining: 0` means the account-level one. Wait for the corresponding `*-Reset` value (seconds) before retrying, or fall back to exponential backoff with jitter. Not every 429 is explained by those headers. A separate per-authenticated-user limit, reported in no `X-RateLimit-*` header, covers OAuth-authenticated requests and signed requests in configurations where the customer-level limit is not in effect — on the operations that use the default throttles. A few operations override those and are governed by the customer-level limit alone. The two do not stack: a signed request governed by the customer-level limit above is not additionally subject to the per-user one. If a 429 arrives with no header at zero — or with no `X-RateLimit-*` headers at all — honour `Retry-After` and back off. Treat the remaining counts as a hint, not a guarantee that the next request will succeed. Because the customer-level limit applies everywhere, any signed request can return 429. **OAuth-authenticated requests are an exception.** They are not subject to the customer-level limit and do not receive `X-RateLimit-Limit`, `X-RateLimit-Remaining` or `X-RateLimit-Reset` — do not wait on those headers or design around a customer-level allowance on this path. The account-level limit still applies to them on the account-data endpoints above, reported in the `X-RateLimit-Account-*` headers. On operations using the default throttles the per-user limit above applies to them as well, so an OAuth request can be rejected while the account headers still show capacity; on the few operations that override those throttles, OAuth callers have no per-user ceiling at all. Drive retries from `Retry-After` and exponential backoff with jitter rather than from the headers. See https://docs.snaptrade.com/docs/ratelimiting.
jeffersongoncalves/laravel-page-cache
1838 Downloads
This Laravel package provides a full-page response cache middleware for stateless public GET pages. It caches 200 responses keyed by a version token, locale, and theme cookie, skips authenticated requests, exposes an X-Page-Cache HIT/MISS header, and offers a static flush() helper to invalidate every cached page at once.
hyperdigital/hd_structureddata
5743 Downloads
Extension for adding structured JSON-LD into page headers