Server on GenHTTP Webserver

Adapters

Mon, 01 Jan 0001 00:00:00 +0000

GenHTTP is both a web server and a web application development framework. Adapters allow to re-use the functionality of the GenHTTP modules in other server frameworks such as ASP.NET Core.

ASP.NET Core

GenHTTP.Adapters.AspNetCore Package on NuGet

This adapter allows to plug in any GenHTTP handler into an existing ASP.NET Core application. The following example will use the listing module to render a graphical file listing when accessing http://localhost:5000/files/ in the browser.

Logging

Mon, 01 Jan 0001 00:00:00 +0000

GenHTTP uses the default logging mechanism of .NET Core and allows to create loggers via the IServer interface. By default, the host will add a console logger.

Logging Information

The following code shows to obtain a logger from the server instance in a custom IHandler implementation. It is recommended to create the logger once in the preparation phase and store the reference somewhere. You can use this pattern anywhere where you have access to IServer (e.g. via request.Server).

Endpoints and Ports

Mon, 01 Jan 0001 00:00:00 +0000

By default, the server will listen on port 8080 for incoming IPv4 or IPv6 connections on any interface. To simply change the port the server will listen on, you can use the Port() directive of the host. Please note, that hosting a server on ports below 1024 will require additional permissions on some operating systems.

 C#
 
 
var host = Host.Create()
 .Handler(...)
 .Port(80);

To configure the server to listen on specific interfaces only, you can Bind() those endpoints explicitly.

Security

Mon, 01 Jan 0001 00:00:00 +0000

This page summarizes security considerations and configuration options when running GenHTTP applications.

General Considerations

GenHTTP is designed to be used as an application server behind a reverse proxy, and therefore does not provide built-in DoS protection (such as IP connection limits or Slowloris prevention). However, compared to many other web service frameworks for C#, it is hardened against - and explicitly tested for - typical attack vectors such as request smuggling, header injection, or malformed chunk attacks.