Libraries tagged by statuses
josantonius/httpstatuscode
6171 Downloads
PHP library to get HTTP status code messages and definitions.
yarri/essence
2928 Downloads
Extracts information about medias on the web, like youtube videos, twitter statuses or blog articles.
xima/xima-typo3-content-planner
3826 Downloads
This extension provides a page status functionality to support the planning of content work.
verbb/postie
17071 Downloads
Get shipping rates, tracking status and print labels with Australia Post, UPS, USPS, FedEx, DHL Express, and more.
t3n/flow-healthstatus
28725 Downloads
Flow Framework package to check the health status of you application
smith197/steamauthentication
541 Downloads
SteamAuthentication is a basic set of PHP files that enable users to login using their steam account to view protected content on your website. it creates a session using their steamid as the sessionID and checks for the session when a user visits the page. It also includes a file which allows you to use their profile information such as their avatar and online status.
sheavescapital/livewire-kanban-board
970 Downloads
Livewire component to show models/data according to its current status on a Kanban board
sametsahindogan/laravel-jwtredis
1773 Downloads
This package allows JWT-authenticated users to be stored and management in Redis with their roles, permissions, statuses and anything you want.
sachoo/phalcon-console-migration
131781 Downloads
Based on sachoo/phalcon-console, this component handle databases migrations (up, down, diff, status, run)
paypaplane/svix-client
15115 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.
lobotomised/laravel-autocrawler
33053 Downloads
A tool to crawl your own laravel installation checking your HTTP status codes
leadtech/http-commons
22390 Downloads
A zero dependency set of definitions to help work with headers and status codes.
lantongxue/php-nohup
11496 Downloads
A library to run a command in the background, it will return the process's pid, and get it's is running status anytime in the another process, and can be stoped anytime. It support Windows, Linux and Mac osx.
havvg/http-exception
13928 Downloads
A collection of exception classes to reflect HTTP status codes.
ctw/ctw-http
113090 Downloads
This package provides utility classes and constants to facilitate common operations of PSR-7 and a group of exceptions which represent HTTP status codes.