Found 33 packages
A lightweight .NET package for working with HTTP status codes and status code descriptions.
HTTP Status Codes (http-status-codes) binding library for Bridge.NET projects.
A Sitefinity widget that switches HTTP status codes.
Event handler plugin for Umbraco that allows users to specify as page properties HTTP Status Codes to be returned.
This is micro library developed by PandaTech to standardize API responses
Generic API Response Builder for common response schema, handling status codes results and response validation in ASP.NET Core.
HttpClient extension methods that return Result<T> instead of throwing. Maps HTTP 4xx/5xx status codes to typed domain errors (NotFoundError, UnauthorizedError, ForbiddenError, ConflictError, ValidationError) and wraps network exceptions in ExceptionError. Configurable via HttpResultOptions.
API proxy. Heartbeat. Simplified payload handling. Simplified content result creation incl. JSON. Simplified IActionResult handling for common HTTP status codes. Media types. Extensions.
Lightweight response helpers for setting headers, writing content, managing status codes, and handling redirect
ASP.NET Core Http integration for MiddleMan.Zero providing automatic conversion of Result objects to IResult with appropriate HTTP status codes.
HTTP Status Code Lookup is a tool for looking up HTTP status code information. It provides descriptions, categories, and common causes for all standard HTTP status codes from 1xx to 5xx.
Specialized result types that can be mapped automatically to HTTP status codes
Middleware that converts unhandled exception into application/json http-response. Follows RESTful way to produce different HTTP status codes for different exception types.
Provides a centralized and consistent set of core constants for the RA Utilities ecosystem. This includes common response types, HTTP status codes, and default messages to streamline development and reduce magic strings.
A .NET library providing unified error handling for ASP.NET Core applications. The package implements middleware that catches exceptions and transforms them into standardized JSON responses with proper HTTP status codes. Key Features: - Global exception handling middleware - Standardized error response format - Built-in support for common exception types - Request correlation tracking - Configurable stack trace visibility - Consistent logging Designed to streamline error handling across microservices and web applications while maintaining proper error tracking and debugging capabilities.
Enables Umbraco editors to be able to check their Umbraco site for broken links. Features - Able to check an entire site, or just a section or even a single page - Completely asychnronous so can check multiple links simultaneously and provide real-time feedback - Caches link status so only checks each unique link once (within a short period) - Works for all types of links - external, internal, HTML, files, images and even CSS and JavaScript files - Provides feedback on errors with help dialogue and an overview of HTTP status codes - Quick edit facilty allows you to easily edit the page that contains the broken link directly within Umbraco - Advanced options allow you to set the timeout period, toggle between viewing all checked links and only links that have problems - You can whitelist HTTP codes and only report on those - You can also configure it to ignore ports (if you are behind a reverse proxy, for example)
A lightweight Result pattern implementation for handling success and failure outcomes in .NET applications with support for error information and HTTP status codes.
ASP.NET Core integration for Linger.Results library, providing extension methods to seamlessly convert Result objects to ActionResults with appropriate HTTP status codes. Simplifies API response handling with RFC 7807 support and automatic status mapping.
The basic premise of the Emesary messaging system is to allow the decoupled operation of the various components that comprise any system - usually within the same process. The basic unit of communication is a Notification, which is passed around to any and or all objects that implement the IReceive interface. Using Interfaces and ihneritance it is possible to pass around Notifications that have special meanings to certain objects and allow them to perform the appropriate function. In our design Notifications are created and sent via a call to NotifyAll. Any object within the system can implement the IReceive interface and register itself with either a Queue (WIP) or a Transmitter to receive all notifications that are sent out. The underlying concept is that one part of a system knows that something needs to be done without needing to know how to do it. The part of the system that needs something done simply creates a notification and sends it out. Once received by the part of the system that is capable of performing the requested Notification the relevant actions will be carried out and a status of OK or Finished returned. See the section on return codes for a complete explanation of these codes and what they mean. ref. http://chateau-logic.com/content/c-wpf-application-plumbing-using-emesary
Source generators for REslava.Result library. Automatically generates extension methods to convert Result types to ASP.NET Core IResult with proper HTTP status codes and ProblemDetails.