"list of all possible http error code with status"
Expose HTTP error codes as Error objects
Custom error that makes use of HTTP error codes to identify different error types.
Error classes for HTTP error codes.
Constants for HTTP error codes
A handler to generate generic http error messages according to http error codes
offgame http error codes list
Http error codes with names and messages
Error manager for handling errors within the classes by creating self defined error codes and parsing them into http error codes
Constants enumerating the HTTP status codes. Based on the Java Apache HttpStatus API.
Error classes for HTTP-error-codes (4xx, 5xx)
Interact with HTTP status code
HTTP status utility
Module Federation Error Codes
Http error codes with names and messages
The map of HTTP status codes from the builtin http module
Ergonomic HTTP Error codes
Utility to lookup HTTP status codes
QRCode / 2d Barcode api with both server side and client side support using canvas
Library to easily style texts with string formatting
Convert HTTP Error Codes to user-friendly text with descriptions
Get the visual width of a string - the number of columns required to display it
Create errors with code and cause properties
Strip ANSI escape codes from a string
Return HTTP error codes while rendering the corresponding error page in Rails.
"sinatra-errorcodes is the sinatra extension that contains a pack of HTTP error status code and message"
As seen here https://www.flickr.com/photos/girliemac/sets/72157628409467125/
As seen here http://httpstatusdogs.com/
The Lob API is organized around REST. Our API is designed to have predictable, resource-oriented URLs and uses HTTP response codes to indicate any API errors. <p> Looking for our [previous documentation](https://lob.github.io/legacy-docs/)?
Raise 4xx and 5xx HTTP status code errors using Errawr
Allows customization of: * Specify which level of notification you would like with an array of optional styles of notification (email, webhooks) * the sender address of the email * the recipient addresses * the text used to prefix the subject line * the HTTP status codes to notify for * the error classes to send emails for * alternatively, the error classes to not notify for * whether to send error emails or just render without sending anything * the HTTP status and status code that gets rendered with specific errors * the view path to the error page templates * custom errors, with custom error templates * define error layouts at application or controller level, or use the controller's own default layout, or no layout at all * get error notification for errors that occur in the console, using notifiable method * Override the gem's handling and rendering with explicit rescue statements inline. * Hooks into `git blame` output so you can get an idea of who (may) have introduced the bug * Hooks into other website services (e.g. you can send exceptions to to Switchub.com) * Can notify of errors occurring in any class/method using notifiable { method } * Can notify of errors in Rake tasks using NotifiedTask.new instead of task * Works with Hoptoad Notifier, so you can notify via SEN and/or Hoptoad for any particular errors. * Tested with Rails 2.3.x, should work with rails 2.2.x, and is apparently not yet compatible with rails 3.
Allows customization of: * Specify which level of notification you would like with an array of optional styles of notification (email, webhooks) * the sender address of the email * the recipient addresses * the text used to prefix the subject line * the HTTP status codes to notify for * the error classes to send emails for * alternatively, the error classes to not notify for * whether to send error emails or just render without sending anything * the HTTP status and status code that gets rendered with specific errors * the view path to the error page templates * custom errors, with custom error templates * define error layouts at application or controller level, or use the controller's own default layout, or no layout at all * get error notification for errors that occur in the console, using notifiable method * Override the gem's handling and rendering with explicit rescue statements inline. * Hooks into `git blame` output so you can get an idea of who (may) have introduced the bug * Hooks into other website services (e.g. you can send exceptions to to Switchub.com)
Allows customization of: * Specify which level of notification you would like with an array of optional styles of notification (email, webhooks) * the sender address of the email * the recipient addresses * the text used to prefix the subject line * the HTTP status codes to notify for * the error classes to send emails for * alternatively, the error classes to not notify for * whether to send error emails or just render without sending anything * the HTTP status and status code that gets rendered with specific errors * the view path to the error page templates * custom errors, with custom error templates * define error layouts at application or controller level, or use the controller's own default layout, or no layout at all * get error notification for errors that occur in the console, using notifiable method * Override the gem's handling and rendering with explicit rescue statements inline. * Hooks into `git blame` output so you can get an idea of who (may) have introduced the bug * Hooks into other website services (e.g. you can send exceptions to to Switchub.com) * Can notify of errors occurring in any class/method using notifiable { method } * Can notify of errors in Rake tasks using NotifiedTask.new instead of task * * NOTE: in environment.rb, specify :lib => 'exception_notifier'
Saferpay JSON application programming interface with a ruby API wrapper built with Net::HTTP Saferpay API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. Saferpay use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients. JSON will be returned in all responses from the API, including errors.
A gem for handling exceptions thrown inside your Rails app. If you include the gem in your application controller, wrangler will render the error pages you configure for each exception or HTTP error code. It will also handle notifying you via email when certain exceptions are raised. Allows for configuration of which exceptions map to which error pages, which exceptions result in emails being sent. Also allows for asynchronous email sending via delayed job so that error pages don't take forever to load (but delayed_job is not required for sending email; wrangler will automatically send email synchronously if delayed_job is not available. . See README for lots of info on how to get started and what configuration options are available.
# Introduction The Dyspatch API is based on the REST paradigm, and features resource based URLs with standard HTTP response codes to indicate errors. We use standard HTTP authentication and request verbs, and all responses are JSON formatted. See our [Implementation Guide](https://docs.dyspatch.io/development/implementing_dyspatch/) for more details on how to implement Dyspatch. ## API Client Libraries Dyspatch provides API Clients for popular languages and web frameworks. - [Java](https://github.com/getdyspatch/dyspatch-java) - [Javascript](https://github.com/getdyspatch/dyspatch-javascript) - [Python](https://github.com/getdyspatch/dyspatch-python) - [C#](https://github.com/getdyspatch/dyspatch-dotnet) - [Go](https://github.com/getdyspatch/dyspatch-golang) - [Ruby](https://github.com/getdyspatch/dyspatch-ruby)
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.