4 repository-uri
Capabilities for calculating or setting HTTP status codes dynamically for API operations.
Distinct from Health Status APIs: Focuses on HTTP response status codes for API operations, not health status or UI status bars.
Explore 4 awesome GitHub repositories matching web development · Dynamic Response Statuses. Refine with filters or upvote what's useful.
This project is a REST-to-gRPC API gateway and JSON reverse proxy that translates RESTful HTTP requests into gRPC service calls. It functions as a protocol buffer proxy generator, providing the tools necessary to bridge JSON-based HTTP traffic with backend gRPC servers. The system distinguishes itself by automating the creation of reverse-proxy servers and stubs through protobuf-driven code generation. It also includes a dedicated OpenAPI specification generator that produces OpenAPI v2 and v3 documents from gRPC service definitions and annotations. The project covers a broad range of integr
Controls the HTTP status code returned to the client by intercepting gRPC metadata.
TypeSpec is a language for defining cloud API shapes and generating OpenAPI, JSON Schema, and client/server code from a single source of truth. It functions as a protocol-agnostic API designer that models REST, gRPC, and other API protocols using a unified, extensible syntax, with a decorator-based metadata system for attaching metadata, validation rules, and lifecycle visibility to API models and operations. The compiler produces OpenAPI 3.0 specifications and other artifacts, and the tool supports declaring API versions and tracking changes to models, properties, and operations across releas
Sets HTTP status codes on return types, defaulting to 200 or 204, and supports unions for multiple responses.
Huma is an OpenAPI REST framework for Go designed for building HTTP services with automatic OpenAPI 3.1 specification generation and JSON Schema validation. It serves as a toolkit for developing REST and RPC APIs with typed inputs and outputs, deriving interactive documentation directly from the source code. The framework distinguishes itself by automating the synchronization between implementation and documentation. It uses a content-negotiation engine to manage multiple serialization formats via client headers and employs a JSON Schema input validator to automatically verify request paramet
Enables the definition of default or dynamically calculated HTTP status codes for each API operation.
Identifies valid profiles by analyzing HTTP response status codes without parsing page content.