apimock-server 5.0.0

HTTP(S) server runtime for apimock: listener loop, request handling, response building.
Documentation

HTTP(S) server runtime for apimock.

Responsibilities

  • Listener binding and the accept loop (HTTP + HTTPS).
  • Per-request dispatch (OPTIONS / middleware / rule sets / dyn_route).
  • Compiling Rhai middlewares from paths recorded in config.
  • Building hyper::Response values from a matched Respond.

What is deliberately not here

  • Rule-set matching logic. That's apimock-routing.
  • Config parsing / validation. That's apimock-config.
  • Server restart policy. The brief is explicit (§7): a running server does not restart itself. It may emit [ReloadHint]; an external control layer decides what to do.