Eigenverft.NetLib.Hosting.SelfHttpWarmup 1.0.0.5-g17613f8942

Eigenverft.NetLib.Hosting.SelfHttpWarmup

Warm up an ASP.NET Core application by sending HTTP GET requests to its own endpoints once the host has started.

✨ At a glance

📦 Installation

dotnet add package Eigenverft.NetLib.Hosting.SelfHttpWarmup

🚀 Quick start

Use the application's actual listening URL and a lightweight endpoint that is available after startup:

using System;
using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.Http;
using Eigenverft.NetLib.Hosting.SelfHttpWarmup;

var builder = WebApplication.CreateBuilder(args);
builder.WebHost.UseUrls("http://localhost:5080");
builder.Services.AddSelfHttpWarmup(
    "http://localhost:5080/health",
    options =>
    {
        options.InitialDelay = TimeSpan.FromSeconds(1);
        options.RequestTimeout = TimeSpan.FromSeconds(3);
    });

var app = builder.Build();
app.MapGet("/health", () => Results.Ok());
await app.RunAsync();

The hosted service waits for ApplicationStarted, then sends each configured target sequentially with GET. The default initial delay is zero and each request has a five-second timeout.

For a lightweight liveness target, the separate Eigenverft.WebLib.HealthProbes package provides a fixed GET/HEAD /health response: GET returns 200 with OK, and HEAD returns 200 without a body. It does not invoke ASP.NET Core health checks or report dependency readiness. Either package can be used without the other.

⚙️ Configure through appsettings

Register the feature and bind the SelfHttpWarmup section:

builder.Services.AddSelfHttpWarmup();

{
  "SelfHttpWarmup": {
    "Enabled": true,
    "InitialDelay": "00:00:01",
    "RequestTimeout": "00:00:05",
    "TargetUrls": [
      "http://localhost:5080/health"
    ]
  }
}

Options binding alone leaves warmup disabled. The URL overloads and the options-action overload enable it automatically. Targets must be absolute HTTP or HTTPS URLs; invalid targets supplied through the direct URL overload are rejected during registration.

The client connects directly without a proxy, does not follow redirects, and has a one-second connection timeout per resolved address. Point it at an address and port served by this process. Request failures and timeouts are logged and do not stop the host. The package depends on Microsoft.Extensions hosting and HTTP abstractions and does not add an ASP.NET Core shared-framework dependency.

🎯 Target frameworks

• net8.0
• net10.0

A .NET 9 consumer can use the compatible net8.0 asset.

🔗 Project links

• Source project
• Solution documentation
• Repository

📄 License

MIT