Libraries tagged by response headers
abordage/laravel-last-modified
8464 Downloads
Setting the Last-Modified header and 304 Not Modified response code if the page hasn't changed since the last visit
dotkernel/dot-response-header
9125 Downloads
DotKernel middleware for setting custom response headers.
los/response-time
58896 Downloads
PHP middleware to add a Response Time header
sloyakuza/laravel-security-headers
7155 Downloads
Adds security related headers to HTTP response.
signify-nz/silverstripe-security-headers
7739 Downloads
Adds configurable security headers to HTTP responses via middleware.
hdvinnie/laravel-security-headers
24930 Downloads
Adds security related headers to HTTP response.
batch.com/headers-bundle
44893 Downloads
A Symfony bundle to easily add headers to your responses.
bepsvpt/laravel-security-header
2279 Downloads
Add security related headers to HTTP response. The package includes Service Providers for easy Laravel integration.
dcarbone/curl-header-extractor
56504 Downloads
Utility to extract headers from PHP CURL to file request.
stevenmaguire/laravel-middleware-csp
106238 Downloads
Provides support for enforcing Content Security Policy with headers in Laravel responses.
stevenmaguire/middleware-csp
145435 Downloads
Provides support for enforcing Content Security Policy with headers in PSR 7 responses.
b13/hydra
9004 Downloads
Allows adding response headers through site config.
middlewares/csp
6784 Downloads
Middleware to add the Content-Security-Policy header to the response
paypaplane/svix-client
10228 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.
softspring/response-headers
6049 Downloads
This component provides response headers configuration for Symfony projects