FluxFlow.Components.Http 1.0.0

There is a newer version of this package available.
See the version list below for details.
dotnet add package FluxFlow.Components.Http --version 1.0.0
                    
NuGet\Install-Package FluxFlow.Components.Http -Version 1.0.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="FluxFlow.Components.Http" Version="1.0.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="FluxFlow.Components.Http" Version="1.0.0" />
                    
Directory.Packages.props
<PackageReference Include="FluxFlow.Components.Http" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add FluxFlow.Components.Http --version 1.0.0
                    
#r "nuget: FluxFlow.Components.Http, 1.0.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package FluxFlow.Components.Http@1.0.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=FluxFlow.Components.Http&version=1.0.0
                    
Install as a Cake Addin
#tool nuget:?package=FluxFlow.Components.Http&version=1.0.0
                    
Install as a Cake Tool

FluxFlow.Components.Http

Reusable HTTP request components for FluxFlow.

Nodes

Node type Shape Purpose
http.request InputOutput, Errors Sends HTTP requests and emits typed responses or request errors.

HTTP Request

{
  "type": "http.request",
  "name": "call-api",
  "baseUrl": "https://example.test",
  "defaultTimeoutMilliseconds": 30000,
  "maxResponseBodyBytes": 1048576,
  "followRedirects": true,
  "treatNonSuccessStatusAsError": false,
  "boundedCapacity": 128
}

http.request consumes HttpRequestInput values and emits HttpResponseOutput values. Network, timeout, cancellation, invalid URL, and body size failures are emitted through HttpErrorOutput on the Errors port. The node continues processing later messages after a per-message failure.

Non-success status codes do not fault the node. Responses are emitted with Success = false. When treatNonSuccessStatusAsError is enabled, the response is still emitted and a matching error item is also emitted.

Runtime Timing

Responses and request errors use the package clock for timestamps and elapsed milliseconds. Existing callers use the default system clock. Hosts and tests can provide a deterministic clock through registration:

registry.RegisterHttpComponents(options => options
    .UseClock(httpClock));

Sender Ownership

The package includes a default per-node sender. Hosts that need named clients, shared clients, custom authentication, tracing, proxy settings, deterministic time, or test doubles can provide IHttpRequestSenderFactory through registration:

registry.RegisterHttpComponents(options => options
    .UseClock(httpClock)
    .UseRequestSenderFactory(myFactory));

The sender factory receives the resolved node options and configured clock. The package disposes senders it creates through the configured factory.

Composition Guidance

Use this package as one part of a host-composed graph. See Component Composition for recommended host boundaries, package boundaries, and extraction timing.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on FluxFlow.Components.Http:

Package Downloads
FluxFlow.Components.Http.AspNetCore

ASP.NET Core HTTP trigger adapter for FluxFlow: maps an endpoint's HttpContext onto the request/reply bridge so an inbound request flows into a graph and the correlated response is written back. The only FluxFlow package that references ASP.NET Core.

FluxFlow.Components.Http.Composition

Canonical HTTP FlowContent/result registration and Designer metadata over host-owned keyed HttpClient resources.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
7.0.0-rc.1 84 9/5/2026
6.0.0 231 8/3/2026
3.0.2 146 7/3/2026
3.0.1 207 7/2/2026
3.0.0 148 6/19/2026
2.0.0 137 6/18/2026
1.2.1 120 6/15/2026
1.2.0 419 6/12/2026
1.1.0 118 6/5/2026
1.0.0 117 6/4/2026
0.2.0-alpha.1 246 6/2/2026
0.1.1-alpha.1 91 6/2/2026
0.1.0-alpha.1 101 6/1/2026

Stable 1.0.0 component package boundary for FluxFlow.Engine 1.0.0 with package-owned contracts, neutral diagnostics, and release readiness documentation.