Skip to content

v1.0.0 — Initial release

Choose a tag to compare

View all tags
@freitasjca freitasjca released this 01 Jun 16:10
· 15 commits to master since this release
v1.0.0
05f380a

v1.0.0 — Initial release

First public release of horse-provider-mormot — a mORMot2-backed transport provider for the Horse web framework.

What this is

A drop-in alternative to Horse's default Indy transport, activated by a single compiler define:

{$DEFINE HORSE_PROVIDER_MORMOT}

uses Horse;
begin
  THorse.Get('/ping', procedure(Req: THorseRequest; Res: THorseResponse)
  begin
    Res.Send('pong');
  end);
  THorse.Listen(9000);
end.

Routes, middleware, and THorseRequest / THorseResponse API are unchanged — switching transports does not require rewriting handlers. The mORMot2 THttpServer runs underneath instead of Indy's thread-per-connection model.

What's included

  • Hybrid interface architecture — IHorseRawRequest / IHorseRawResponse with backward-compatible TInterfacedWebRequest / TInterfacedWebResponse adapters so every existing Horse middleware (CORS, JWT, Jhonson, …) works unchanged.
  • Pre-pipeline request validation — URL length, header limits, body size, method allowlist, request-smuggling guards before the Horse pipeline is entered.
  • Pooled THorseContext — pre-warmed object pool, zero allocation on the hot path, Reset wipes every security-sensitive field between requests.
  • Graceful drain on shutdown — SEC-30 active-request counter; Listen returns only after in-flight requests complete.
  • Application-type cross-product units — Console (default), VCL, Daemon (Windows Service + Linux daemon in one unit), FPC.Daemon, FPC.LCL, FPC.HTTPApplication. Same .dpr compiles for both Windows and Linux targets.
  • TLS via OpenSSL — both libssl 1.1.x and 3.x accepted at runtime; mormot2static static-link variant supported for self-contained deployments.

mORMot2 interop notes

  • Loopback RemoteIP normalised — mORMot2 defaults RemoteIPLocalHostAsVoidInServers to True, reporting loopback connections with an empty RemoteIP. Horse middleware that consumes Req.RawWebRequest.RemoteAddr (rate limiters, audit loggers) needs a stable peer IP, so the provider sets this global to False at unit init. See doc/implementation-notes.md for the side effect this has on co-resident mORMot servers in the same process.
  • Multipart file uploads — MultiPartFormDataDecode returns inline RawByteString parts; the bridge synthesises a TMemoryStream per file part and routes it through ContentFields.AddStream. See Known limitations below.

Requirements

Dependency Version Notes
Delphi 10.4 Sydney or later Uses inline var, System.Threading
FPC 3.2.0 or later For the FPC.* application-type units
Horse >= 3.1.98 PATCH-HORSE-2 three-axis define release
mORMot2 recent master Install per synopse/mORMot2 instructions; on Delphi the mormot2static precompiled blobs are required

Installation

boss install horse-provider-mormot

mORMot2 itself is installed manually (clone + search paths). See the README for the full setup including the static-blob download.

Tested platforms

  • Windows x86 / x64 (IOCP; also http.sys via THttpApiServer swap)
  • Linux x64 (epoll)
  • macOS ARM64

Known limitations

  • [FOLLOW-UP-MEM-1] — multipart-with-file uploads leak one TMemoryStream per request until the pool is torn down. Functionally correct (uploads work, content arrives intact), but memory accumulates under sustained upload load. Two proper fixes (pool-side stream tracking, or a Horse upstream TObjectDictionary([doOwnsValues]) patch) are documented in doc/implementation-notes.md — appropriate for low-throughput services, dev/test, and short-lived processes; not yet appropriate for high-throughput production upload endpoints.

Documentation

Acknowledgements

Assets 2
Loading