Alethic.Node.Http
1.0.1-pre.27
dotnet add package Alethic.Node.Http --version 1.0.1-pre.27
NuGet\Install-Package Alethic.Node.Http -Version 1.0.1-pre.27
<PackageReference Include="Alethic.Node.Http" Version="1.0.1-pre.27" />
<PackageVersion Include="Alethic.Node.Http" Version="1.0.1-pre.27" />
<PackageReference Include="Alethic.Node.Http" />
paket add Alethic.Node.Http --version 1.0.1-pre.27
#r "nuget: Alethic.Node.Http, 1.0.1-pre.27"
#:package Alethic.Node.Http@1.0.1-pre.27
#addin nuget:?package=Alethic.Node.Http&version=1.0.1-pre.27&prerelease
#tool nuget:?package=Alethic.Node.Http&version=1.0.1-pre.27&prerelease
Alethic.Node.Http
The protocol by which a JavaScript application's fetch handler is served from .NET, shared by
Alethic.Node.AspNetCore and
Alethic.Node.AspNet, so one application is served by either.
Referenced through them; documented here because it is what the application sees.
The application is a CommonJS bundle whose default export has a fetch function, or is one:
export default {
fetch(request, env, ctx) { /* return a Response */ },
};
request: aRequestatBaseUri(http://node.invalid/) plus the path below the mount. The visitor's address is inX-Forwarded-Proto,X-Forwarded-HostandX-Forwarded-Prefix, written by the host.env: the strings inEnvironment, new per request.ctx:waitUntil(promise)andpassThroughOnException().- The
Response's status, headers and body become the host's, lessContent-LengthandTransfer-Encoding.
ResponseBody is Streamed, each chunk sent as produced, or Buffered, nothing sent until done, so a failure
partway through can still be answered.
| Product | Versions 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 is compatible. 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 was computed. 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. |
| .NET Framework | net472 is compatible. net48 was computed. net481 was computed. |
-
.NETFramework 4.7.2
- Alethic.Node (>= 1.0.1-pre.27)
-
net8.0
- Alethic.Node (>= 1.0.1-pre.27)
-
net9.0
- Alethic.Node (>= 1.0.1-pre.27)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Alethic.Node.Http:
| Package | Downloads |
|---|---|
|
Alethic.Node.AspNetCore
Server-side rendering for ASP.NET Core on a Node runtime embedded in the process, over Alethic.Node's pooled engines: the rendering engine over the application's fetch export, and endpoint mapping driven by the application's own route manifest. |
|
|
Alethic.Node.AspNet
Node embedded in an ASP.NET (System.Web) application on .NET Framework, over Alethic.Node's pooled engines: the application's pool, Node work done on behalf of a request with the request's own thread serving what it asks of the page, fetch answered in process by the site's own handlers, and whole pages from a JavaScript application's fetch handler, mounted on ASP.NET routes. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.0.1-pre.27 | 69 | 10/4/2026 |
| 1.0.1-pre.25 | 71 | 10/4/2026 |
| 1.0.0 | 316 | 10/3/2026 |
| 1.0.0-pre.37 | 86 | 10/3/2026 |