Found 120 packages
Provides a programming interface for modern HTTP applications, including HTTP client components that allow applications to consume web services over HTTP and HTTP components that can be used by both clients and servers for parsing HTTP headers. Commonly Used Types: System.Net.Http.HttpResponseMessage System.Net.Http.DelegatingHandler System.Net.Http.HttpRequestException System.Net.Http.HttpClient System.Net.Http.MultipartContent System.Net.Http.Headers.HttpContentHeaders System.Net.Http.HttpClientHandler System.Net.Http.StreamContent System.Net.Http.FormUrlEncodedContent System.Net.Http.HttpMessageHandler When using NuGet 3.x this package requires at least version 3.4.
Contains types that represent HTTP request and response headers. This library is used with classes such as System.Net.HttpWebRequest and System.Net.HttpWebResponse and allows developers to query/edit header names/values. Commonly Used Types: System.Net.HttpRequestHeader System.Net.HttpResponseHeader System.Net.WebHeaderCollection When using NuGet 3.x this package requires at least version 3.4.
Provides older classes (such as HttpWebRequest and HttpWebResponse) for sending HTTP requests and receiving HTTP responses from a resource identified by a URI. Developers should prefer the classes in the System.Net.Http package. Commonly Used Types: System.Net.HttpWebRequest System.Net.HttpWebResponse System.Net.HttpRequestHeader System.Net.WebException System.Net.WebExceptionStatus System.Net.WebRequest System.Net.WebResponse When using NuGet 3.x this package requires at least version 3.4.
A modern async HTTP client for REST APIs. Its fluent interface lets you send an HTTP request and parse the response in one go.
This is a FluentAssertions extension over the HttpResponseMessage object. It provides specific assertions and outputs rich erros messages that include the HTTP Request and Response. This version **DOES NOT** depend on the commercial version of the FluentAssertions library (>= 8.0.0).
This package contains specific CoreKraft Web Response builders (Binary, Http and XML).
Test/mock (3rd party) code reliant on HttpClient, WebClient, HttpWebRequest and WebRequest.Create()
HttpResponseManager is a portable library. Using this library application can call and get Web API response using GET and PUT methods. User can also include the Headers while calling APIs.
Allows querying WCF Web Api endpoints that expose IQueryable<T>, with full query support for nested relationships, etc. Does not deal with response deserialization. Look for HttpEntityClient for that.
Adds helper methods to HttpResponse and HttpRequest to make working with Htmx (https://htmx.org) easier.
Query/Handle Http Request created by Responsible.Core for Web Api.
WatchDog is a Realtime Message, Event, HTTP (Request & Response) and Exception logger and viewer for ASP.Net Core Web Apps and APIs. It allows developers log and view messages, events, http requests made to their web application and also exception caught during runtime in their web applications, all in Realtime. It leverages SignalR for real-time monitoring and LiteDb a Serverless MongoDB-like database with no configuration with the option of using your external databases.
A fake implementation of HttpResponseBase
Calls httprequest and returns HttpResponse in a way easier than the native.
Provides the ability to send HttpWebRequest and get HttpWebResponses without a server. You can mock all available properties from HttpWebResponse .Net object with a json configuration file. This tool is not intrusive. With dependency injection you can simply switch between your own implementation of IHttpRequester and the implementation contained in this package
This is a AwesomeAssertions extension over the HttpResponseMessage object. It provides specific assertions and outputs rich erros messages that include the HTTP Request and Response.
A simple Test Client built on top of ASP.NET Web API Help Page. Optimized the JSON display ui of http response.
WebJobs extension for Azure Functions to treat HttpTriggers like regular HTTP requests for the purposes of logging in Application Insights. If an HttpTrigger returns a 4xx or 5xx response, it will be logged as an error in Application Insights. If you are using Isolated functions, do not use this package directly. Use Element.Azure.Functions.Worker.Extensions.HttpTelemetry instead.
The "Web API Correlator" enables correlation functionality for Web API and interconnected Web API services within a service composition. With the increasing complexity of modern distributed SOA systems containing interconnected services, it becomes crucial to determine causal relationships between the services and its clients. It is important to understand the various components that were part of a request flow to support critical scenarios such as health monitoring, troubleshooting, and root cause analysis. For this reason many frameworks provide correlation capability. For example, WCF has built-in correlation functionality. Although Web API creates (Request.GetCorrelationId()) and carries the Correlation Id throughout the HTTP request handling process, taking care of thread context switches as part of asynchronous nature of processing Web API requests, the boundary for this Correlation Id is limited to a single server-side request-response cycle. In other words, the Correlation Id Web API provides "out of the box" is limited to a single service boundary. In essence, Web API lacks ability to correlate processes between client and server, as well as interconnected services chains applicable to many distributed SOA applications. Effectively, we lose ability to relate multiple events immediately as a process crosses the service boundary; the information about multiple linked events within the system become dispersed data records rather representing the related nature of those events. The "Web API Correlator" enables absent functionality by transferring the Correlation Id from API Client (browser or .NET HttpClient, or .NET WebClient) to the server, propagating it into the server-side Web API process, and forwarding to interconnected Web API services within a service composition. The "Web API Correlator" contains correlation component for .NET, and offers a plugin for jQuery AJAX. The jQuery plug-in manages and maintains the Correlation Id on the client-side and ensures the Correlation Id being added to all AJAX requests.
The Throttling Suite provides throttling control capabilities to the .NET Web API applications. It is highly customizable product, yet simple to use. The implementation supports all available hosting options provisioning equal functionality for IIS-hosted and OWIN self-hosted solutions. It is specifically designed to throttle high performance and high throughput Web API applications. The library contains multiple controller types implementing different throttling algorithms: Linear throttling - limits the number of calls by enforcing consistent delay between consequent requests; Short Average - limits the number of calls by specified number of requests per configured duration; it does not intend to limit the overall number of requests, but rather assures blocking excessive requests; this strategy is very helpful to cut the requests floods; Long Average - limits the number of calls by specified number of requests per configured duration; this strategy limits an overall number of calls within long time duration; this is also known as applying penalty to the client for excessive application use. Each throttling controller is capable of unique client determination and management. The throttling for any end-point, or set of end-points can be configured either for the entire application, or per-client. It does not purely rely on client IP address, allowing multiple clients from the same network concurrently making requests to the server. The Throttling Suite allows setting multiple controllers within the application and applying each to a pre-filtered traffic. The filters are also configurable. The Throttling Suite provides two modes: real blocking mode when request is blocked with 429 HTTP Status code and log-only mode. The code is highly optimized having very low memory impact. The throttling evaluation functionality takes less than 0.3 ms to run. The v1.2 is updated to include "Retry-After" response header in the blocked response helping API client to negotiate the request rate with API server side. The v1.2 also allows to ignore the actual request URL substituting one with Throttling controller instance scope. This provides the benefit to count requests for multiple API endpoints toward the same throttling threshold. The v1.3 enables configuration from the code rather than XML *.config file.