@forklaunch/core 0.2.37 → 0.3.0

package/lib/http/index.mjs

@@ -0,0 +1,2122 @@
+// src/http/guards/isForklaunchRouter.ts
+function isForklaunchRouter(maybeForklaunchRouter) {
+  return maybeForklaunchRouter != null && typeof maybeForklaunchRouter === "object" && "basePath" in maybeForklaunchRouter && "routes" in maybeForklaunchRouter && Array.isArray(maybeForklaunchRouter.routes);
+}
+
+// src/http/guards/isConstrainedForklaunchRouter.ts
+function isConstrainedForklaunchRouter(maybeForklaunchExpressLikeRouter) {
+  return isForklaunchRouter(maybeForklaunchExpressLikeRouter) && "requestHandler" in maybeForklaunchExpressLikeRouter;
+}
+
+// src/http/guards/isExpressLikeSchemaHandler.ts
+import { extractArgumentNames } from "@forklaunch/common";
+function isExpressLikeSchemaHandler(middleware2) {
+  const extractedArgumentNames = typeof middleware2 === "function" && new Set(
+    extractArgumentNames(middleware2).map(
+      (argumentName) => argumentName.toLowerCase()
+    )
+  );
+  return extractedArgumentNames && extractedArgumentNames.size <= 3;
+}
+
+// src/http/guards/isForklaunchExpressLikeRouter.ts
+function isForklaunchExpressLikeRouter(maybeForklaunchExpressLikeRouter) {
+  return isConstrainedForklaunchRouter(
+    maybeForklaunchExpressLikeRouter
+  ) && "basePath" in maybeForklaunchExpressLikeRouter && "internal" in maybeForklaunchExpressLikeRouter;
+}
+
+// src/http/guards/isPathParamContractDetails.ts
+function isPathParamHttpContractDetails(maybePathParamHttpContractDetails) {
+  return maybePathParamHttpContractDetails != null && typeof maybePathParamHttpContractDetails === "object" && "name" in maybePathParamHttpContractDetails && "summary" in maybePathParamHttpContractDetails && "responses" in maybePathParamHttpContractDetails && maybePathParamHttpContractDetails.name != null && maybePathParamHttpContractDetails.summary != null && maybePathParamHttpContractDetails.responses != null;
+}
+
+// src/http/guards/isHttpContractDetails.ts
+function isHttpContractDetails(maybeContractDetails) {
+  return isPathParamHttpContractDetails(maybeContractDetails) && "body" in maybeContractDetails && maybeContractDetails.body != null;
+}
+
+// src/http/guards/isTypedHandler.ts
+function isTypedHandler(maybeTypedHandler) {
+  return maybeTypedHandler != null && typeof maybeTypedHandler === "object" && "_typedHandler" in maybeTypedHandler && maybeTypedHandler._typedHandler === true;
+}
+
+// src/http/middleware/request/auth.middleware.ts
+import { jwtVerify } from "jose";
+var invalidAuthorizationTokenFormat = [
+  401,
+  "Invalid Authorization token format."
+];
+var invalidAuthorizationSubject = [
+  403,
+  "Invalid Authorization subject."
+];
+var invalidAuthorizationTokenPermissions = [
+  403,
+  "Invalid Authorization permissions."
+];
+var invalidAuthorizationTokenRoles = [
+  403,
+  "Invalid Authorization roles."
+];
+var invalidAuthorizationToken = [
+  403,
+  "Invalid Authorization token."
+];
+var invalidAuthorizationLogin = [
+  403,
+  "Invalid Authorization login."
+];
+async function checkAuthorizationToken(authorizationMethod, authorizationToken, req) {
+  if (authorizationToken == null) {
+    return [401, "No Authorization token provided."];
+  }
+  const [tokenPrefix, token] = authorizationToken.split(" ");
+  let resourceId;
+  switch (authorizationMethod.method) {
+    case "jwt": {
+      if (tokenPrefix !== "Bearer") {
+        return invalidAuthorizationTokenFormat;
+      }
+      try {
+        const decodedJwt = await jwtVerify(
+          token,
+          new TextEncoder().encode(
+            // TODO: Check this at application startup if there is any route with jwt checking
+            process.env.JWT_SECRET
+          )
+        );
+        if (!decodedJwt.payload.sub) {
+          return invalidAuthorizationSubject;
+        }
+        resourceId = decodedJwt.payload.sub;
+      } catch (error) {
+        console.error(error);
+        return invalidAuthorizationToken;
+      }
+      break;
+    }
+    case "basic": {
+      if (authorizationToken !== "Basic") {
+        return invalidAuthorizationTokenFormat;
+      }
+      const [username, password] = Buffer.from(token, "base64").toString("utf-8").split(":");
+      if (!username || !password) {
+        return invalidAuthorizationTokenFormat;
+      }
+      if (!authorizationMethod.login(username, password)) {
+        return invalidAuthorizationLogin;
+      }
+      resourceId = username;
+      break;
+    }
+    case "other":
+      if (tokenPrefix !== authorizationMethod.tokenPrefix) {
+        return invalidAuthorizationTokenFormat;
+      }
+      resourceId = authorizationMethod.decodeResource(token);
+      break;
+  }
+  if (authorizationMethod.allowedPermissions || authorizationMethod.forbiddenPermissions) {
+    if (!authorizationMethod.mapPermissions) {
+      return [500, "No permission mapping function provided."];
+    }
+    const resourcePermissions = await authorizationMethod.mapPermissions(
+      resourceId,
+      req
+    );
+    if (authorizationMethod.allowedPermissions) {
+      if (resourcePermissions.intersection(authorizationMethod.allowedPermissions).size === 0) {
+        return invalidAuthorizationTokenPermissions;
+      }
+    }
+    if (authorizationMethod.forbiddenPermissions) {
+      if (resourcePermissions.intersection(
+        authorizationMethod.forbiddenPermissions
+      ).size !== 0) {
+        return invalidAuthorizationTokenPermissions;
+      }
+    }
+  }
+  if (authorizationMethod.allowedRoles || authorizationMethod.forbiddenRoles) {
+    if (!authorizationMethod.mapRoles) {
+      return [500, "No role mapping function provided."];
+    }
+    const resourceRoles = await authorizationMethod.mapRoles(resourceId, req);
+    if (authorizationMethod.allowedRoles) {
+      if (resourceRoles.intersection(authorizationMethod.allowedRoles).size === 0) {
+        return invalidAuthorizationTokenRoles;
+      }
+    }
+    if (authorizationMethod.forbiddenRoles) {
+      if (resourceRoles.intersection(authorizationMethod.forbiddenRoles).size !== 0) {
+        return invalidAuthorizationTokenRoles;
+      }
+    }
+  }
+  return [401, "Invalid Authorization method."];
+}
+async function parseRequestAuth(req, res, next) {
+  console.debug("[MIDDLEWARE] parseRequest started");
+  const auth = req.contractDetails.auth;
+  if (auth) {
+    const errorAndMessage = await checkAuthorizationToken(
+      auth,
+      req.headers[(auth.method === "other" ? auth.headerName : void 0) ?? "Authorization"],
+      req
+    );
+    if (Array.isArray(errorAndMessage)) {
+      res.status(errorAndMessage[0]).send(errorAndMessage[1]);
+      next?.(new Error(errorAndMessage[1]));
+    }
+  }
+  next?.();
+}
+
+// src/http/middleware/request/cors.middleware.ts
+import corsMiddleware from "cors";
+function cors(req, res, next) {
+  console.debug("[MIDDLEWARE] cors started");
+  if (req.method === "OPTIONS") {
+    res.cors = true;
+  }
+  corsMiddleware()(req, res, next ?? (() => {
+  }));
+}
+
+// src/http/middleware/request/createContext.middleware.ts
+import { v4 } from "uuid";
+function createContext(schemaValidator) {
+  return (req, res, next) => {
+    console.debug("[MIDDLEWARE] createRequestContext started");
+    req.schemaValidator = schemaValidator;
+    let correlationId = v4();
+    if (req.headers["x-correlation-id"]) {
+      correlationId = req.headers["x-correlation-id"];
+    }
+    res.setHeader("x-correlation-id", correlationId);
+    req.context = {
+      correlationId
+    };
+    next?.();
+  };
+}
+
+// src/http/middleware/request/enrichDetails.middleware.ts
+function enrichDetails(contractDetails, requestSchema, responseSchemas) {
+  return (req, res, next) => {
+    console.debug("[MIDDLEWARE] enrichRequestDetails started");
+    req.contractDetails = contractDetails;
+    req.requestSchema = requestSchema;
+    res.responseSchemas = responseSchemas;
+    next?.();
+  };
+}
+
+// src/http/guards/isResponseShape.ts
+function isResponseShape(maybeResponseShape) {
+  return maybeResponseShape != null && "body" in maybeResponseShape && "query" in maybeResponseShape && "params" in maybeResponseShape && "headers" in maybeResponseShape;
+}
+
+// src/http/middleware/request/parse.middleware.ts
+function parse(req, _res, next) {
+  console.debug("[MIDDLEWARE] parseRequest started");
+  const request = {
+    params: req.params,
+    query: req.query,
+    headers: req.headers,
+    body: req.body
+  };
+  const parsedRequest = req.schemaValidator.parse(req.requestSchema, request);
+  if (parsedRequest.ok && isResponseShape(parsedRequest.value)) {
+    req.body = parsedRequest.value.body;
+    req.params = parsedRequest.value.params;
+    req.query = parsedRequest.value.query;
+    req.headers = parsedRequest.value.headers;
+  }
+  if (!parsedRequest.ok) {
+    switch (req.contractDetails.options?.requestValidation) {
+      default:
+      case "error":
+        next?.(new Error(`Invalid request: ${parsedRequest.error}`));
+        break;
+      case "warning":
+        console.warn(`Invalid request: ${parsedRequest.error}`);
+        break;
+      case "none":
+        break;
+    }
+  }
+  next?.();
+}
+
+// src/http/router/expressLikeRouter.ts
+var ForklaunchExpressLikeRouter = class {
+  constructor(basePath, schemaValidator, internal) {
+    this.schemaValidator = schemaValidator;
+    this.internal = internal;
+    this.basePath = basePath;
+    this.internal.use(createContext(this.schemaValidator));
+    this.internal.use(cors);
+  }
+  requestHandler;
+  routers = [];
+  routes = [];
+  basePath;
+  /**
+   * Resolves middlewares based on the contract details.
+   *
+   * @param {PathParamHttpContractDetails<SV> | HttpContractDetails<SV>} contractDetails - The contract details.
+   * @returns {MiddlewareHandler<SV>[]} - The resolved middlewares.
+   */
+  #resolveMiddlewares(contractDetails, requestSchema, responseSchemas) {
+    return [
+      enrichDetails(contractDetails, requestSchema, responseSchemas),
+      parse,
+      parseRequestAuth
+    ];
+  }
+  /**
+   * Parses and runs the controller handler with error handling.
+   *
+   * @template P - The type of request parameters.
+   * @template ResBodyMap - The type of response body.
+   * @template ReqBody - The type of request body.
+   * @template ReqQuery - The type of request query.
+   * @template LocalsObj - The type of local variables.
+   * @template StatusCode - The type of status code.
+   * @param {MiddlewareHandler<SV, P, ResBodyMap | string, ReqBody, ReqQuery, LocalsObj, StatusCode>} requestHandler - The request handler.
+   * @returns {ExpressMiddlewareHandler} - The Express request handler.
+   */
+  #parseAndRunControllerHandler(requestHandler) {
+    return async (req, res, next) => {
+      if (!requestHandler) {
+        throw new Error("Controller handler is not defined");
+      }
+      try {
+        await requestHandler(req, res, next);
+      } catch (error) {
+        next?.(error);
+        console.error(error);
+        if (!res.headersSent) {
+          res.status(500).send("Internal Server Error");
+        }
+      }
+    };
+  }
+  /**
+   * Extracts the controller handler from the provided handlers.
+   *
+   * @template P - The type of request parameters.
+   * @template ResBodyMap - The type of response body.
+   * @template ReqBody - The type of request body.
+   * @template ReqQuery - The type of request query.
+   * @template LocalsObj - The type of local variables.
+   * @param {MiddlewareHandler<SV, P, ResBodyMap, ReqBody, ReqQuery, LocalsObj>[]} handlers - The provided handlers.
+   * @returns {MiddlewareHandler<SV, P, ResBodyMap, ReqBody, ReqQuery, LocalsObj>} - The extracted controller handler.
+   * @throws {Error} - Throws an error if the last argument is not a handler.
+   */
+  #extractControllerHandler(handlers) {
+    const controllerHandler = handlers.pop();
+    if (typeof controllerHandler !== "function") {
+      throw new Error(
+        `Last argument must be a handler, received: ${controllerHandler}`
+      );
+    }
+    return controllerHandler;
+  }
+  #compile(contractDetails) {
+    const schemaValidator = this.schemaValidator;
+    const requestSchema = schemaValidator.compile(
+      schemaValidator.schemify({
+        ...contractDetails.params ? { params: contractDetails.params } : {},
+        ...contractDetails.requestHeaders ? { headers: contractDetails.requestHeaders } : {},
+        ...contractDetails.query ? { query: contractDetails.query } : {},
+        ...isHttpContractDetails(contractDetails) && contractDetails.body ? { body: contractDetails.body } : {}
+      })
+    );
+    const responseEntries = {
+      400: schemaValidator.string,
+      401: schemaValidator.string,
+      403: schemaValidator.string,
+      404: schemaValidator.string,
+      500: schemaValidator.string,
+      ...isPathParamHttpContractDetails(contractDetails) || isHttpContractDetails(contractDetails) ? { ...contractDetails.responses } : {}
+    };
+    const responseSchemas = {
+      responses: {},
+      ...contractDetails.responseHeaders ? {
+        headers: schemaValidator.compile(
+          schemaValidator.schemify(contractDetails.responseHeaders)
+        )
+      } : {}
+    };
+    Object.entries(responseEntries).forEach(([code, responseShape]) => {
+      responseSchemas.responses[Number(code)] = schemaValidator.compile(
+        schemaValidator.schemify(responseShape)
+      );
+    });
+    return {
+      requestSchema,
+      responseSchemas
+    };
+  }
+  /**
+   * Executes request locally, applying parameters
+   *
+   * @param handlers {ExpressLikeHandler<SV>}
+   * @param controllerHandler
+   * @returns
+   */
+  #localParamRequest(handlers, controllerHandler) {
+    return async (route, request) => {
+      let statusCode;
+      let responseMessage;
+      const responseHeaders = {};
+      const req = {
+        params: request?.params ?? {},
+        query: request?.query ?? {},
+        headers: request?.headers ?? {},
+        body: request?.body ?? {},
+        path: route
+      };
+      const res = {
+        status: (code) => {
+          statusCode = code;
+          return res;
+        },
+        send: (message) => {
+          responseMessage = message;
+        },
+        json: (body) => {
+          responseMessage = body;
+        },
+        jsonp: (body) => {
+          responseMessage = body;
+        },
+        setHeader: (key, value) => {
+          responseHeaders[key] = value;
+        }
+      };
+      let cursor = handlers.shift();
+      if (cursor) {
+        for (const fn of handlers) {
+          await cursor(req, res, (err) => {
+            if (err) {
+              throw err;
+            }
+            cursor = fn;
+          });
+        }
+        await cursor(req, res, async (err) => {
+          if (err) {
+            throw err;
+          }
+        });
+      }
+      const cHandler = controllerHandler;
+      await cHandler(req, res, (err) => {
+        if (err) {
+          throw err;
+        }
+      });
+      return {
+        code: statusCode,
+        response: responseMessage,
+        headers: responseHeaders
+      };
+    };
+  }
+  registerRoute(method, path, registrationMethod, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareAndTypedHandler) {
+    if (isTypedHandler(contractDetailsOrMiddlewareOrTypedHandler)) {
+      const { contractDetails, handlers } = contractDetailsOrMiddlewareOrTypedHandler;
+      return this.registerRoute(
+        method,
+        path,
+        registrationMethod,
+        contractDetails,
+        ...handlers
+      );
+    } else {
+      const maybeTypedHandler = middlewareOrMiddlewareAndTypedHandler[middlewareOrMiddlewareAndTypedHandler.length - 1];
+      if (isTypedHandler(maybeTypedHandler)) {
+        const { contractDetails, handlers } = maybeTypedHandler;
+        return this.registerRoute(
+          method,
+          path,
+          registrationMethod,
+          contractDetails,
+          ...middlewareOrMiddlewareAndTypedHandler.concat(handlers)
+        );
+      } else {
+        if (isExpressLikeSchemaHandler(contractDetailsOrMiddlewareOrTypedHandler) || isTypedHandler(contractDetailsOrMiddlewareOrTypedHandler)) {
+          throw new Error("Contract details are not defined");
+        }
+        const contractDetails = contractDetailsOrMiddlewareOrTypedHandler;
+        const handlers = middlewareOrMiddlewareAndTypedHandler.filter(
+          (handler) => isExpressLikeSchemaHandler(handler)
+        );
+        if (!isHttpContractDetails(contractDetails) && !isPathParamHttpContractDetails(contractDetails)) {
+          throw new Error(
+            "Contract details are malformed for route definition"
+          );
+        }
+        this.routes.push({
+          basePath: this.basePath,
+          path,
+          method,
+          contractDetails
+        });
+        const { requestSchema, responseSchemas } = this.#compile(contractDetails);
+        const controllerHandler = this.#extractControllerHandler(handlers);
+        registrationMethod.bind(this.internal)(
+          path,
+          ...this.#resolveMiddlewares(contractDetails, requestSchema, responseSchemas).concat(
+            handlers
+          ),
+          this.#parseAndRunControllerHandler(controllerHandler)
+        );
+        return this.#localParamRequest(
+          handlers,
+          controllerHandler
+        );
+      }
+    }
+  }
+  #extractHandlers(handlers, processMiddleware) {
+    const last = handlers.pop();
+    let finalHandlers = last ? [last] : [];
+    if (isTypedHandler(last)) {
+      finalHandlers = last.handlers;
+    }
+    handlers.forEach((handler) => {
+      if (isTypedHandler(handler)) {
+        throw new Error(
+          "Only the last argument supplied to this function can be a typed handler. Please use only middleware."
+        );
+      }
+    });
+    const middleware2 = processMiddleware ? handlers.map(processMiddleware) : handlers;
+    return [...middleware2, ...finalHandlers];
+  }
+  #extractMiddlewareFromEnrichedTypedHandlerArray(handlers) {
+    return this.#extractHandlers(handlers);
+  }
+  #extractNestableMiddlewareFromEnrichedTypedHandlerArray(handlers) {
+    return this.#extractHandlers(
+      handlers,
+      (handler) => isForklaunchExpressLikeRouter(handler) ? handler.internal : handler
+    );
+  }
+  #processTypedHandlerOrMiddleware(handler, middleware2) {
+    if (isTypedHandler(handler)) {
+      middleware2.push(...handler.handlers);
+    } else if (isExpressLikeSchemaHandler(handler)) {
+      middleware2.push(handler);
+    }
+  }
+  #extractMiddlewareAsRouterHandlers(contractDetailsOrMiddlewareOrTypedHandler, middlewareOrMiddlewareWithTypedHandler) {
+    const middleware2 = [];
+    this.#processTypedHandlerOrMiddleware(contractDetailsOrMiddlewareOrTypedHandler, middleware2);
+    middleware2.push(
+      ...this.#extractMiddlewareFromEnrichedTypedHandlerArray(middlewareOrMiddlewareWithTypedHandler)
+    );
+    return middleware2;
+  }
+  #extractNestableMiddlewareAsRouterHandlers(contractDetailsOrMiddlewareOrTypedHandler, middlewareOrMiddlewareWithTypedHandler) {
+    const middleware2 = [];
+    this.#processTypedHandlerOrMiddleware(
+      contractDetailsOrMiddlewareOrTypedHandler,
+      middleware2
+    );
+    if (isForklaunchExpressLikeRouter(
+      contractDetailsOrMiddlewareOrTypedHandler
+    )) {
+      middleware2.push(contractDetailsOrMiddlewareOrTypedHandler.internal);
+    }
+    middleware2.push(
+      ...this.#extractNestableMiddlewareFromEnrichedTypedHandlerArray(middlewareOrMiddlewareWithTypedHandler)
+    );
+    return middleware2;
+  }
+  registerMiddlewareHandler(registrationMethod, pathOrContractDetailsOrMiddlewareOrTypedHandler, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) {
+    const middleware2 = [];
+    if (typeof pathOrContractDetailsOrMiddlewareOrTypedHandler === "string") {
+      middleware2.push(
+        ...this.#extractMiddlewareAsRouterHandlers(
+          contractDetailsOrMiddlewareOrTypedHandler,
+          middlewareOrMiddlewareWithTypedHandler
+        )
+      );
+      const path = pathOrContractDetailsOrMiddlewareOrTypedHandler;
+      registrationMethod.bind(this.internal)(path, ...middleware2);
+    } else {
+      middleware2.push(
+        ...this.#extractMiddlewareAsRouterHandlers(
+          pathOrContractDetailsOrMiddlewareOrTypedHandler,
+          (isExpressLikeSchemaHandler(contractDetailsOrMiddlewareOrTypedHandler) || isTypedHandler(contractDetailsOrMiddlewareOrTypedHandler) ? [contractDetailsOrMiddlewareOrTypedHandler] : []).concat(middlewareOrMiddlewareWithTypedHandler)
+        )
+      );
+      registrationMethod.bind(this.internal)(...middleware2);
+    }
+    return this;
+  }
+  registerNestableMiddlewareHandler(registrationMethod, pathOrContractDetailsOrMiddlewareOrTypedHandler, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) {
+    const middleware2 = [];
+    let path;
+    if (typeof pathOrContractDetailsOrMiddlewareOrTypedHandler === "string") {
+      middleware2.push(
+        ...this.#extractNestableMiddlewareAsRouterHandlers(
+          contractDetailsOrMiddlewareOrTypedHandler,
+          middlewareOrMiddlewareWithTypedHandler
+        )
+      );
+      path = pathOrContractDetailsOrMiddlewareOrTypedHandler;
+    } else {
+      if (isConstrainedForklaunchRouter(
+        pathOrContractDetailsOrMiddlewareOrTypedHandler
+      )) {
+        path = pathOrContractDetailsOrMiddlewareOrTypedHandler.basePath;
+      }
+      middleware2.push(
+        ...this.#extractNestableMiddlewareAsRouterHandlers(
+          pathOrContractDetailsOrMiddlewareOrTypedHandler,
+          (isExpressLikeSchemaHandler(contractDetailsOrMiddlewareOrTypedHandler) || isTypedHandler(contractDetailsOrMiddlewareOrTypedHandler) || isConstrainedForklaunchRouter(
+            contractDetailsOrMiddlewareOrTypedHandler
+          ) ? [contractDetailsOrMiddlewareOrTypedHandler] : []).concat(middlewareOrMiddlewareWithTypedHandler)
+        )
+      );
+    }
+    if (path) {
+      registrationMethod.bind(this.internal)(path, ...middleware2);
+    } else {
+      registrationMethod.bind(this.internal)(...middleware2);
+    }
+    return this;
+  }
+  use = (pathOrContractDetailsOrMiddlewareOrTypedHandler, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    [
+      pathOrContractDetailsOrMiddlewareOrTypedHandler,
+      contractDetailsOrMiddlewareOrTypedHandler,
+      ...middlewareOrMiddlewareWithTypedHandler
+    ].forEach((arg) => {
+      if (isForklaunchRouter(arg)) {
+        this.routers.push(arg);
+      }
+    });
+    return this.registerNestableMiddlewareHandler(
+      this.internal.use,
+      pathOrContractDetailsOrMiddlewareOrTypedHandler,
+      contractDetailsOrMiddlewareOrTypedHandler,
+      ...middlewareOrMiddlewareWithTypedHandler
+    );
+  };
+  all = (pathOrContractDetailsOrMiddlewareOrTypedHandler, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    return this.registerMiddlewareHandler(
+      this.internal.all,
+      pathOrContractDetailsOrMiddlewareOrTypedHandler,
+      contractDetailsOrMiddlewareOrTypedHandler,
+      ...middlewareOrMiddlewareWithTypedHandler
+    );
+  };
+  connect = (pathOrContractDetailsOrMiddlewareOrTypedHandler, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    return this.registerMiddlewareHandler(
+      this.internal.connect,
+      pathOrContractDetailsOrMiddlewareOrTypedHandler,
+      contractDetailsOrMiddlewareOrTypedHandler,
+      ...middlewareOrMiddlewareWithTypedHandler
+    );
+  };
+  /**
+   * Registers a GET route with the specified contract details and handler handlers.
+   *
+   * @template P - The type of request parameters.
+   * @template ResBodyMap - The type of response body.
+   * @template ReqBody - The type of request body.
+   * @template ReqQuery - The type of request query.
+   * @template LocalsObj - The type of local variables.
+   * @param {string} path - The path for the route.
+   * @param {PathParamHttpContractDetails<SV, P, ResBodyMap, ReqQuery>} contractDetails - The contract details.
+   * @param {...SchemaHandler<SV, P, ResBodyMap, ReqBody, ReqQuery, LocalsObj>[]} handlers - The handler handlers.
+   * @returns {ExpressRouter} - The Express router.
+   */
+  get = (path, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    return {
+      get: this.registerRoute(
+        "get",
+        path,
+        this.internal.get,
+        contractDetailsOrMiddlewareOrTypedHandler,
+        ...middlewareOrMiddlewareWithTypedHandler
+      )
+    };
+  };
+  /**
+   * Registers a POST route with the specified contract details and handler handlers.
+   *
+   * @template P - The type of request parameters.
+   * @template ResBodyMap - The type of response body.
+   * @template ReqBody - The type of request body.
+   * @template ReqQuery - The type of request query.
+   * @template LocalsObj - The type of local variables.
+   * @param {string} path - The path for the route.
+   * @param {HttpContractDetails<SV, P, ResBodyMap, ReqBody, ReqQuery>} contractDetails - The contract details.
+   * @param {...SchemaHandler<SV, P, ResBodyMap, ReqBody, ReqQuery, LocalsObj>[]} handlers - The handler handlers.
+   * @returns {ExpressRouter} - The Expxwress router.
+   */
+  post = (path, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    return {
+      post: this.registerRoute(
+        "post",
+        path,
+        this.internal.post,
+        contractDetailsOrMiddlewareOrTypedHandler,
+        ...middlewareOrMiddlewareWithTypedHandler
+      )
+    };
+  };
+  /**
+   * Registers a PUT route with the specified contract details and handler handlers.
+   *
+   * @template P - The type of request parameters.
+   * @template ResBodyMap - The type of response body.
+   * @template ReqBody - The type of request body.
+   * @template ReqQuery - The type of request query.
+   * @template LocalsObj - The type of local variables.
+   * @param {string} path - The path for the route.
+   * @param {HttpContractDetails<SV, P, ResBodyMap, ReqBody, ReqQuery>} contractDetails - The contract details.
+   * @param {...SchemaHandler<SV, P, ResBodyMap, ReqBody, ReqQuery, LocalsObj>[]} handlers - The handler handlers.
+   * @returns {ExpressRouter} - The Express router.
+   */
+  put = (path, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    return {
+      put: this.registerRoute(
+        "put",
+        path,
+        this.internal.put,
+        contractDetailsOrMiddlewareOrTypedHandler,
+        ...middlewareOrMiddlewareWithTypedHandler
+      )
+    };
+  };
+  /**
+   * Registers a PATCH route with the specified contract details and handler handlers.
+   *
+   * @template P - The type of request parameters.
+   * @template ResBodyMap - The type of response body.
+   * @template ReqBody - The type of request body.
+   * @template ReqQuery - The type of request query.
+   * @template LocalsObj - The type of local variables.
+   * @param {string} path - The path for the route.
+   * @param {HttpContractDetails<SV, P, ResBodyMap, ReqBody, ReqQuery>} contractDetails - The contract details.
+   * @param {...SchemaHandler<SV, P, ResBodyMap, ReqBody, ReqQuery, LocalsObj>[]} handlers - The handler handlers.
+   * @returns {ExpressRouter} - The Express router.
+   */
+  patch = (path, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    return {
+      patch: this.registerRoute(
+        "patch",
+        path,
+        this.internal.patch,
+        contractDetailsOrMiddlewareOrTypedHandler,
+        ...middlewareOrMiddlewareWithTypedHandler
+      )
+    };
+  };
+  /**
+   * Registers a DELETE route with the specified contract details and handler handlers.
+   *
+   * @template P - The type of request parameters.
+   * @template ResBodyMap - The type of response body.
+   * @template ReqBody - The type of request body.
+   * @template ReqQuery - The type of request query.
+   * @template LocalsObj - The type of local variables.
+   * @param {string} path - The path for the route.
+   * @param {PathParamHttpContractDetails<SV, P, ResBodyMap, ReqQuery>} contractDetails - The contract details.
+   * @param {...SchemaHandler<SV, P, ResBodyMap, ReqBody, ReqQuery, LocalsObj>[]} handlers - The handler handlers.
+   * @returns {ExpressRouter} - The Express router.
+   */
+  delete = (path, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    return {
+      delete: this.registerRoute(
+        "delete",
+        path,
+        this.internal.delete,
+        contractDetailsOrMiddlewareOrTypedHandler,
+        ...middlewareOrMiddlewareWithTypedHandler
+      )
+    };
+  };
+  /**
+   * Registers a OPTIONS route with the specified contract details and handler handlers.
+   *
+   * @template P - The type of request parameters.
+   * @template ResBodyMap - The type of response body.
+   * @template ReqBody - The type of request body.
+   * @template ReqQuery - The type of request query.
+   * @template LocalsObj - The type of local variables.
+   * @param {string} path - The path for the route.
+   * @param {PathParamHttpContractDetails<SV, P, ResBodyMap, ReqQuery>} contractDetails - The contract details.
+   * @param {...SchemaHandler<SV, P, ResBodyMap, ReqBody, ReqQuery, LocalsObj>[]} handlers - The handler handlers.
+   * @returns {ExpressRouter} - The Express router.
+   */
+  options = (path, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    return {
+      options: this.registerRoute(
+        "options",
+        path,
+        this.internal.options,
+        contractDetailsOrMiddlewareOrTypedHandler,
+        ...middlewareOrMiddlewareWithTypedHandler
+      )
+    };
+  };
+  /**
+   * Registers a HEAD route with the specified contract details and handler handlers.
+   *
+   * @template P - The type of request parameters.
+   * @template ResBodyMap - The type of response body.
+   * @template ReqBody - The type of request body.
+   * @template ReqQuery - The type of request query.
+   * @template LocalsObj - The type of local variables.
+   * @param {string} path - The path for the route.
+   * @param {PathParamHttpContractDetails<SV, P, ResBodyMap, ReqQuery>} contractDetails - The contract details.
+   * @param {...SchemaHandler<SV, P, ResBodyMap, ReqBody, ReqQuery, LocalsObj>[]} handlers - The handler handlers.
+   * @returns {ExpressRouter} - The Express router.
+   */
+  head = (path, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    return {
+      head: this.registerRoute(
+        "head",
+        path,
+        this.internal.head,
+        contractDetailsOrMiddlewareOrTypedHandler,
+        ...middlewareOrMiddlewareWithTypedHandler
+      )
+    };
+  };
+  /**
+   * Registers a TRACE route with the specified contract details and handler handlers.
+   *
+   * @template P - The type of request parameters.
+   * @template ResBodyMap - The type of response body.
+   * @template ReqBody - The type of request body.
+   * @template ReqQuery - The type of request query.
+   * @template LocalsObj - The type of local variables.
+   * @param {string} path - The path for the route.
+   * @param {PathParamHttpContractDetails<SV, P, ResBodyMap, ReqQuery>} contractDetails - The contract details.
+   * @param {...SchemaHandler<SV, P, ResBodyMap, ReqBody, ReqQuery, LocalsObj>[]} handlers - The handler handlers.
+   * @returns {ExpressRouter} - The Express router.
+   */
+  trace = (path, contractDetailsOrMiddlewareOrTypedHandler, ...middlewareOrMiddlewareWithTypedHandler) => {
+    return {
+      trace: this.registerRoute(
+        "trace",
+        path,
+        this.internal.trace,
+        contractDetailsOrMiddlewareOrTypedHandler,
+        ...middlewareOrMiddlewareWithTypedHandler
+      )
+    };
+  };
+};
+
+// src/http/application/expressLikeApplication.ts
+var ForklaunchExpressLikeApplication = class extends ForklaunchExpressLikeRouter {
+  /**
+   * Creates an instance of the Application class.
+   *
+   * @param {SV} schemaValidator - The schema validator.
+   */
+  constructor(schemaValidator, internal) {
+    super("/", schemaValidator, internal);
+    this.schemaValidator = schemaValidator;
+    this.internal = internal;
+  }
+};
+
+// src/http/handlers/typedHandler.ts
+function typedHandler(_schemaValidator, _pathOrContractDetails, contractMethodOrContractDetails, contractDetailsOrHandler, ...handlerArray) {
+  let contractDetails;
+  let handlers;
+  if (typeof contractMethodOrContractDetails === "string") {
+    if (typeof contractDetailsOrHandler !== "function") {
+      contractDetails = contractDetailsOrHandler;
+    } else {
+      throw new Error("Invalid definition for contract details");
+    }
+    handlers = handlerArray;
+  } else {
+    contractDetails = contractMethodOrContractDetails;
+    if (typeof contractDetailsOrHandler === "function") {
+      handlers = [contractDetailsOrHandler, ...handlerArray];
+    } else {
+      throw new Error("Invalid definition for handler");
+    }
+  }
+  return {
+    _typedHandler: true,
+    contractDetails,
+    handlers
+  };
+}
+
+// src/http/handlers/delete.ts
+var delete_ = (_schemaValidator, path, contractDetails, ...handlers) => {
+  return typedHandler(_schemaValidator, path, "delete", contractDetails, ...handlers);
+};
+
+// src/http/handlers/get.ts
+var get = (_schemaValidator, path, contractDetails, ...handlers) => {
+  return typedHandler(_schemaValidator, path, "get", contractDetails, ...handlers);
+};
+
+// src/http/handlers/head.ts
+var head = (_schemaValidator, path, contractDetails, ...handlers) => {
+  return typedHandler(_schemaValidator, path, "head", contractDetails, ...handlers);
+};
+
+// src/http/handlers/middleware.ts
+var middleware = (_schemaValidator, path, contractDetails, ...handlers) => {
+  return typedHandler(_schemaValidator, path, "middleware", contractDetails, ...handlers);
+};
+
+// src/http/handlers/options.ts
+var options = (_schemaValidator, path, contractDetails, ...handlers) => {
+  return typedHandler(_schemaValidator, path, "options", contractDetails, ...handlers);
+};
+
+// src/http/handlers/patch.ts
+var patch = (_schemaValidator, path, contractDetails, ...handlers) => {
+  return typedHandler(_schemaValidator, path, "patch", contractDetails, ...handlers);
+};
+
+// src/http/handlers/post.ts
+var post = (_schemaValidator, path, contractDetails, ...handlers) => {
+  return typedHandler(_schemaValidator, path, "post", contractDetails, ...handlers);
+};
+
+// src/http/handlers/put.ts
+var put = (_schemaValidator, path, contractDetails, ...handlers) => {
+  return typedHandler(_schemaValidator, path, "put", contractDetails, ...handlers);
+};
+
+// src/http/handlers/trace.ts
+var trace = (_schemaValidator, path, contractDetails, ...handlers) => {
+  return typedHandler(_schemaValidator, path, "trace", contractDetails, ...handlers);
+};
+
+// src/http/utils/httpStatusCodes.ts
+var HTTPStatuses = {
+  /**
+   * The initial part of a request has been received and has not yet been
+   * rejected by the server. The server intends to send a final response after
+   * the request has been fully received and acted upon.
+   *
+   * When the request contains an Expect header field that includes a
+   * 100-continue expectation, the 100 response indicates that the server
+   * wishes to receive the request payload body. The client ought to continue
+   * sending the request and discard the 100 response.
+   *
+   * If the request did not contain an Expect header field containing the
+   * 100-continue expectation, the client can simply discard this interim
+   * response.
+   */
+  100: "Continue",
+  /**
+   * The server understands and is willing to comply with the client's request,
+   * via the Upgrade header field, for a change in the application protocol
+   * being used on this connection.
+   *
+   * The server MUST generate an Upgrade header field in the response that
+   * indicates which protocol(s) will be switched to immediately after the
+   * empty line that terminates the 101 response.
+   *
+   * It is assumed that the server will only agree to switch protocols when it
+   * is advantageous to do so. For example, switching to a newer version of
+   * HTTP might be advantageous over older versions, and switching to a
+   * real-time, synchronous protocol might be advantageous when delivering
+   * resources that use such features.
+   */
+  101: "Switching Protocols",
+  /**
+   * An interim response used to inform the client that the server has accepted
+   * the complete request, but has not yet completed it.
+   *
+   * This status code SHOULD only be sent when the server has a reasonable
+   * expectation that the request will take significant time to complete. As
+   * guidance, if a method is taking longer than 20 seconds (a reasonable, but
+   * arbitrary value) to process the server SHOULD return a 102 (Processing)
+   * response. The server MUST send a final response after the request has been
+   * completed.
+   *
+   * Methods can potentially take a long period of time to process, especially
+   * methods that support the Depth header. In such cases the client may
+   * time-out the connection while waiting for a response. To prevent this the
+   * server may return a 102 Processing status code to indicate to the client
+   * that the server is still processing the method.
+   */
+  102: "Processing",
+  /**
+   * The request has succeeded.
+   *
+   * Aside from responses to CONNECT, a 200 response always has a payload,
+   * though an origin server MAY generate a payload body of zero length. If no
+   * payload is desired, an origin server ought to send 204 No Content instead.
+   * For CONNECT, no payload is allowed because the successful result is a
+   * tunnel, which begins immediately after the 200 response header section.
+   *
+   * A 200 response is cacheable by default; i.e., unless otherwise indicated
+   * by the method definition or explicit cache controls.
+   */
+  200: "OK",
+  /**
+   * The request has been fulfilled and has resulted in one or more new
+   * resources being created.
+   *
+   * The primary resource created by the request is identified by either a
+   * Location header field in the response or, if no Location field is
+   * received, by the effective request URI.
+   *
+   * The 201 response payload typically describes and links to the resource(s)
+   * created. See Section 7.2 of RFC7231 for a discussion of the meaning and
+   * purpose of validator header fields, such as ETag and Last-Modified, in a
+   * 201 response.
+   */
+  201: "Created",
+  /**
+   * The request has been accepted for processing, but the processing has not
+   * been completed. The request might or might not eventually be acted upon,
+   * as it might be disallowed when processing actually takes place.
+   *
+   * There is no facility in HTTP for re-sending a status code from an
+   * asynchronous operation.
+   *
+   * The 202 response is intentionally noncommittal. Its purpose is to allow a
+   * server to accept a request for some other process (perhaps a
+   * batch-oriented process that is only run once per day) without requiring
+   * that the user agent's connection to the server persist until the process
+   * is completed. The representation sent with this response ought to describe
+   * the request's current status and point to (or embed) a status monitor that
+   * can provide the user with an estimate of when the request will be
+   * fulfilled.
+   */
+  202: "Accepted",
+  /**
+   * The request was successful but the enclosed payload has been modified from
+   * that of the origin server's 200 OK response by a transforming proxy.
+   *
+   * This status code allows the proxy to notify recipients when a
+   * transformation has been applied, since that knowledge might impact later
+   * decisions regarding the content. For example, future cache validation
+   * requests for the content might only be applicable along the same request
+   * path (through the same proxies).
+   *
+   * The 203 response is similar to the Warning code of 214 Transformation
+   * Applied, which has the advantage of being applicable to responses with any
+   * status code.
+   *
+   * A 203 response is cacheable by default; i.e., unless otherwise indicated
+   * by the method definition or explicit cache controls.
+   */
+  203: "Non-authoritative Information",
+  /**
+   * The server has successfully fulfilled the request and that there is no
+   * additional content to send in the response payload body.
+   *
+   * Metadata in the response header fields refer to the target resource and
+   * its selected representation after the requested action was applied.
+   *
+   * A 204 response is terminated by the first empty line after the header
+   * fields because it cannot contain a message body.
+   *
+   * A 204 response is cacheable by default; i.e., unless otherwise indicated
+   * by the method definition or explicit cache controls.
+   */
+  204: "No Content",
+  /**
+   * He server has fulfilled the request and desires that the user agent reset
+   * the "document view", which caused the request to be sent, to its original
+   * state as received from the origin server.
+   *
+   * This response is intended to support a common data entry use case where
+   * the user receives content that supports data entry (a form, notepad,
+   * canvas, etc.), enters or manipulates data in that space, causes the
+   * entered data to be submitted in a request, and then the data entry
+   * mechanism is reset for the next entry so that the user can easily
+   * initiate another input action.
+   *
+   * Since the 205 status code implies that no additional content will be
+   * provided, a server MUST NOT generate a payload in a 205 response. In
+   * other words, a server MUST do one of the following for a 205 response: a)
+   * indicate a zero-length body for the response by including a
+   * Content-Length header field with a value of 0; b) indicate a zero-length
+   * payload for the response by including a Transfer-Encoding header field
+   * with a value of chunked and a message body consisting of a single chunk
+   * of zero-length; or, c) close the connection immediately after sending the
+   * blank line terminating the header section.
+   */
+  205: "Reset Content",
+  /**
+   * The server is successfully fulfilling a range request for the target
+   * resource by transferring one or more parts of the selected representation
+   * that correspond to the satisfiable ranges found in the request's Range
+   * header field.
+   *
+   * If a single part is being transferred, the server generating the 206
+   * response MUST generate a Content-Range header field, describing what range
+   * of the selected representation is enclosed, and a payload consisting of
+   * the range.
+   *
+   * If multiple parts are being transferred, the server generating the 206
+   * response MUST generate a "multipart/byteranges" payload2, and a
+   * Content-Type header field containing the multipart/byteranges media type
+   * and its required boundary parameter. To avoid confusion with single-part
+   * responses, a server MUST NOT generate a Content-Range header field in the
+   * HTTP header section of a multiple part response (this field will be sent
+   * in each part instead).
+   *
+   * Within the header area of each body part in the multipart payload, the
+   * server MUST generate a Content-Range header field corresponding to the
+   * range being enclosed in that body part. If the selected representation
+   * would have had a Content-Type header field in a 200 OK response, the
+   * server SHOULD generate that same Content-Type field in the header area of
+   * each body part.
+   *
+   * When multiple ranges are requested, a server MAY coalesce any of the
+   * ranges that overlap, or that are separated by a gap that is smaller than
+   * the overhead of sending multiple parts, regardless of the order in which
+   * the corresponding byte-range-spec appeared in the received Range header
+   * field. Since the typical overhead between parts of a multipart/byteranges
+   * payload is around 80 bytes, depending on the selected representation's
+   * media type and the chosen boundary parameter length, it can be less
+   * efficient to transfer many small disjoint parts than it is to transfer the
+   * entire selected representation.
+   *
+   * A server MUST NOT generate a multipart response to a request for a single
+   * range, since a client that does not request multiple parts might not
+   * support multipart responses. However, a server MAY generate a
+   * multipart/byteranges payload with only a single body part if multiple
+   * ranges were requested and only one range was found to be satisfiable or
+   * only one range remained after coalescing. A client that cannot process a
+   * multipart/byteranges response MUST NOT generate a request that asks for
+   * multiple ranges.
+   *
+   * When a multipart response payload is generated, the server SHOULD send the
+   * parts in the same order that the corresponding byte-range-spec appeared in
+   * the received Range header field, excluding those ranges that were deemed
+   * unsatisfiable or that were coalesced into other ranges. A client that
+   * receives a multipart response MUST inspect the Content-Range header field
+   * present in each body part in order to determine which range is contained
+   * in that body part; a client cannot rely on receiving the same ranges that
+   * it requested, nor the same order that it requested.
+   *
+   * When a 206 response is generated, the server MUST generate the following
+   * header fields, in addition to those required above, if the field would
+   * have been sent in a 200 OK response to the same request: Date,
+   * Cache-Control, ETag, Expires, Content-Location, and Vary.
+   *
+   * If a 206 is generated in response to a request with an If-Range header
+   * field, the sender SHOULD NOT generate other representation header fields
+   * beyond those required above, because the client is understood to already
+   * have a prior response containing those header fields. Otherwise, the
+   * sender MUST generate all of the representation header fields that would
+   * have been sent in a 200 OK response to the same request.
+   *
+   * A 206 response is cacheable by default; i.e., unless otherwise indicated
+   * by explicit cache controls.
+   */
+  206: "Partial Content",
+  /**
+   * A Multi-Status response conveys information about multiple resources in
+   * situations where multiple status codes might be appropriate.
+   *
+   * The default Multi-Status response body is a text/xml or application/xml
+   * HTTP entity with a 'multistatus' root element. Further elements contain
+   * 200, 300, 400, and 500 series status codes generated during the method
+   * invocation. 100 series status codes SHOULD NOT be recorded in a 'response'
+   * XML element.
+   *
+   * Although '207' is used as the overall response status code, the recipient
+   * needs to consult the contents of the multistatus response body for further
+   * information about the success or failure of the method execution. The
+   * response MAY be used in success, partial success and also in failure
+   * situations.
+   *
+   * The 'multistatus' root element holds zero or more 'response' elements in
+   * any order, each with information about an individual resource. Each
+   * 'response' element MUST have an 'href' element to identify the resource.
+   *
+   * A Multi-Status response uses one out of two distinct formats for
+   * representing the status:
+   *
+   * 1. A 'status' element as child of the 'response' element indicates the
+   * status of the message execution for the identified resource as a whole.
+   * Some method definitions provide information about specific status codes
+   * clients should be prepared to see in a response. However, clients MUST be
+   * able to handle other status codes, using the generic rules defined in
+   * RFC2616 Section 10.
+   *
+   * 2. For PROPFIND and PROPPATCH, the format has been extended using the
+   * 'propstat' element instead of 'status', providing information about
+   * individual properties of a resource. This format is specific to PROPFIND
+   * and PROPPATCH, and is described in detail in RFC4918 Section 9.1 and
+   * RFC4918 Section 9.2.
+   */
+  207: "Multi-Status",
+  /**
+   * Used inside a DAV: propstat response element to avoid enumerating the
+   * internal members of multiple bindings to the same collection repeatedly.
+   *
+   * For each binding to a collection inside the request's scope, only one will
+   * be reported with a 200 status, while subsequent DAV:response elements for
+   * all other bindings will use the 208 status, and no DAV:response elements
+   * for their descendants are included.
+   *
+   * Note that the 208 status will only occur for "Depth: infinity" requests,
+   * and that it is of particular importance when the multiple collection
+   * bindings cause a bind loop.
+   *
+   * A client can request the DAV:resource-id property in a PROPFIND request to
+   * guarantee that they can accurately reconstruct the binding structure of a
+   * collection with multiple bindings to a single resource.
+   *
+   * For backward compatibility with clients not aware of the 208 status code
+   * appearing in multistatus response bodies, it SHOULD NOT be used unless the
+   * client has signaled support for this specification using the "DAV" request
+   * header. Instead, a 508 Loop Detected status should be returned when a
+   * binding loop is discovered. This allows the server to return the 508 as
+   * the top-level return status, if it discovers it before it started the
+   * response, or in the middle of a multistatus, if it discovers it in the
+   * middle of streaming out a multistatus response.
+   */
+  208: "Already Reported",
+  /**
+   * The server has fulfilled a GET request for the resource, and the response
+   * is a representation of the result of one or more instance-manipulations
+   * applied to the current instance.
+   *
+   * The actual current instance might not be available except by combining
+   * this response with other previous or future responses, as appropriate for
+   * the specific instance-manipulation(s). If so, the headers of the resulting
+   * instance are the result of combining the headers from the 226 response and
+   * the other instances, following the rules in section 13.5.3 of the HTTP/1.1
+   * specification.
+   *
+   * The request MUST have included an A-IM header field listing at least one
+   * instance-manipulation. The response MUST include an Etag header field
+   * giving the entity tag of the current instance.
+   *
+   * A response received with a status code of 226 MAY be stored by a cache and
+   * used in reply to a subsequent request, subject to the HTTP expiration
+   * mechanism and any Cache-Control headers, and to the requirements in
+   * section 10.6.
+   *
+   * A response received with a status code of 226 MAY be used by a cache, in
+   * conjunction with a cache entry for the base instance, to create a cache
+   * entry for the current instance.
+   */
+  226: "IM Used",
+  /**
+   * The target resource has more than one representation, each with its own
+   * more specific identifier, and information about the alternatives is being
+   * provided so that the user (or user agent) can select a preferred
+   * representation by redirecting its request to one or more of those
+   * identifiers.
+   *
+   * In other words, the server desires that the user agent engage in reactive
+   * negotiation to select the most appropriate representation(s) for its
+   * needs.
+   *
+   * If the server has a preferred choice, the server SHOULD generate a
+   * Location header field containing a preferred choice's URI reference. The
+   * user agent MAY use the Location field value for automatic redirection.
+   *
+   * For request methods other than HEAD, the server SHOULD generate a payload
+   * in the 300 response containing a list of representation metadata and URI
+   * reference(s) from which the user or user agent can choose the one most
+   * preferred. The user agent MAY make a selection from that list
+   * automatically if it understands the provided media type. A specific format
+   * for automatic selection is not defined by this specification because HTTP
+   * tries to remain orthogonal to the definition of its payloads. In practice,
+   * the representation is provided in some easily parsed format believed to be
+   * acceptable to the user agent, as determined by shared design or content
+   * negotiation, or in some commonly accepted hypertext format.
+   *
+   * A 300 response is cacheable by default; i.e., unless otherwise indicated
+   * by the method definition or explicit cache controls.
+   *
+   * Note: The original proposal for the 300 status code defined the URI header
+   * field as providing a list of alternative representations, such that it
+   * would be usable for 200, 300, and 406 responses and be transferred in
+   * responses to the HEAD method. However, lack of deployment and disagreement
+   * over syntax led to both URI and Alternates (a subsequent proposal) being
+   * dropped from this specification. It is possible to communicate the list
+   * using a set of Link header fields3, each with a relationship of
+   * "alternate", though deployment is a chicken-and-egg problem.
+   */
+  300: "Multiple Choices",
+  /**
+   * The target resource has been assigned a new permanent URI and any future
+   * references to this resource ought to use one of the enclosed URIs.
+   *
+   * Clients with link-editing capabilities ought to automatically re-link
+   * references to the effective request URI to one or more of the new
+   * references sent by the server, where possible.
+   *
+   * The server SHOULD generate a Location header field in the response
+   * containing a preferred URI reference for the new permanent URI. The user
+   * agent MAY use the Location field value for automatic redirection. The
+   * server's response payload usually contains a short hypertext note with a
+   * hyperlink to the new URI(s).
+   *
+   * Note: For historical reasons, a user agent MAY change the request method
+   * from POST to GET for the subsequent request. If this behavior is
+   * undesired, the 307 Temporary Redirect status code can be used instead.
+   *
+   * A 301 response is cacheable by default; i.e., unless otherwise indicated
+   * by the method definition or explicit cache controls.
+   */
+  301: "Moved Permanently",
+  /**
+   * The target resource resides temporarily under a different URI. Since the
+   * redirection might be altered on occasion, the client ought to continue to
+   * use the effective request URI for future requests.
+   *
+   * The server SHOULD generate a Location header field in the response
+   * containing a URI reference for the different URI. The user agent MAY use
+   * the Location field value for automatic redirection. The server's response
+   * payload usually contains a short hypertext note with a hyperlink to the
+   * different URI(s).
+   *
+   * Note: For historical reasons, a user agent MAY change the request method
+   * from POST to GET for the subsequent request. If this behavior is
+   * undesired, the 307 Temporary Redirect status code can be used instead.
+   */
+  302: "Found",
+  /**
+   * The server is redirecting the user agent to a different resource, as
+   * indicated by a URI in the Location header field, which is intended to
+   * provide an indirect response to the original request.
+   *
+   * A user agent can perform a retrieval request targeting that URI (a GET or
+   * HEAD request if using HTTP), which might also be redirected, and present
+   * the eventual result as an answer to the original request. Note that the
+   * new URI in the Location header field is not considered equivalent to the
+   * effective request URI.
+   *
+   * This status code is applicable to any HTTP method. It is primarily used
+   * to allow the output of a POST action to redirect the user agent to a
+   * selected resource, since doing so provides the information corresponding
+   * to the POST response in a form that can be separately identified,
+   * bookmarked, and cached, independent of the original request.
+   *
+   * A 303 response to a GET request indicates that the origin server does not
+   * have a representation of the target resource that can be transferred by
+   * the server over HTTP. However, the Location field value refers to a
+   * resource that is descriptive of the target resource, such that making a
+   * retrieval request on that other resource might result in a representation
+   * that is useful to recipients without implying that it represents the
+   * original target resource. Note that answers to the questions of what can
+   * be represented, what representations are adequate, and what might be a
+   * useful description are outside the scope of HTTP.
+   *
+   * Except for responses to a HEAD request, the representation of a 303
+   * response ought to contain a short hypertext note with a hyperlink to the
+   * same URI reference provided in the Location header field.
+   */
+  303: "See Other",
+  /**
+   * A conditional GET or HEAD request has been received and would have
+   * resulted in a 200 OK response if it were not for the fact that the
+   * condition evaluated to false.
+   *
+   * In other words, there is no need for the server to transfer a
+   * representation of the target resource because the request indicates that
+   * the client, which made the request conditional, already has a valid
+   * representation; the server is therefore redirecting the client to make
+   * use of that stored representation as if it were the payload of a 200 OK
+   * response.
+   *
+   * The server generating a 304 response MUST generate any of the following
+   * header fields that would have been sent in a 200 OK response to the same
+   * request: Cache-Control, Content-Location, Date, ETag, Expires, and Vary.
+   *
+   * Since the goal of a 304 response is to minimize information transfer when
+   * the recipient already has one or more cached representations, a sender
+   * SHOULD NOT generate representation metadata other than the above listed
+   * fields unless said metadata exists for the purpose of guiding cache
+   * updates (e.g., Last-Modified might be useful if the response does not have
+   * an ETag field).
+   *
+   * Requirements on a cache that receives a 304 response are defined in
+   * Section 4.3.4 of RFC7234. If the conditional request originated with an
+   * outbound client, such as a user agent with its own cache sending a
+   * conditional GET to a shared proxy, then the proxy SHOULD forward the
+   * 304 response to that client.
+   *
+   * A 304 response cannot contain a message-body; it is always terminated by
+   * the first empty line after the header fields.
+   */
+  304: "Not Modified",
+  /**
+   * Defined in a previous version of this specification and is now deprecated,
+   * due to security concerns regarding in-band configuration of a proxy.
+   */
+  305: "Use Proxy",
+  /**
+   * The target resource resides temporarily under a different URI and the user
+   * agent MUST NOT change the request method if it performs an automatic
+   * redirection to that URI.
+   *
+   * Since the redirection can change over time, the client ought to continue
+   * using the original effective request URI for future requests.
+   *
+   * The server SHOULD generate a Location header field in the response
+   * containing a URI reference for the different URI. The user agent MAY use
+   * the Location field value for automatic redirection. The server's response
+   * payload usually contains a short hypertext note with a hyperlink to the
+   * different URI(s).
+   *
+   * Note: This status code is similar to 302 Found, except that it does not
+   * allow changing the request method from POST to GET. This specification
+   * defines no equivalent counterpart for 301 Moved Permanently (RFC7238,
+   * however, proposes defining the status code 308 Permanent Redirect for
+   * this purpose).
+   */
+  307: "Temporary Redirect",
+  /**
+   * The target resource has been assigned a new permanent URI and any future
+   * references to this resource ought to use one of the enclosed URIs.
+   *
+   * Clients with link editing capabilities ought to automatically re-link
+   * references to the effective request URI to one or more of the new
+   * references sent by the server, where possible.
+   *
+   * The server SHOULD generate a Location header field in the response
+   * containing a preferred URI reference for the new permanent URI. The user
+   * agent MAY use the Location field value for automatic redirection. The
+   * server's response payload usually contains a short hypertext note with a
+   * hyperlink to the new URI(s).
+   *
+   * A 308 response is cacheable by default; i.e., unless otherwise indicated
+   * by the method definition or explicit cache controls.
+   *
+   * Note: This status code is similar to 301 Moved Permanently, except that it
+   * does not allow changing the request method from POST to GET.
+   */
+  308: "Permanent Redirect",
+  /**
+   * The 400 (Bad Request) status code indicates that the server cannot or
+   * will not process the request due to something that is perceived to be
+   * a client error (e.g., malformed request syntax, invalid request
+   * message framing, or deceptive request routing).
+   */
+  400: "Bad Request",
+  /**
+   * The request has not been applied because it lacks valid authentication
+   * credentials for the target resource.
+   *
+   * The server generating a 401 response MUST send a WWW-Authenticate header
+   * field containing at least one challenge applicable to the target resource.
+   *
+   * If the request included authentication credentials, then the 401 response
+   * indicates that authorization has been refused for those credentials. The
+   * user agent MAY repeat the request with a new or replaced Authorization
+   * header field. If the 401 response contains the same challenge as the
+   * prior response, and the user agent has already attempted authentication at
+   * least once, then the user agent SHOULD present the enclosed representation
+   * to the user, since it usually contains relevant diagnostic information.
+   */
+  401: "Unauthorized",
+  /**
+   * The 402 (Payment Required) status code is reserved for future use.
+   */
+  402: "Payment Required",
+  /**
+   * The 403 (Forbidden) status code indicates that the server understood
+   * the request but refuses to authorize it.  A server that wishes to
+   * make public why the request has been forbidden can describe that
+   * reason in the response payload (if any).
+   *
+   * If authentication credentials were provided in the request, the
+   * server considers them insufficient to grant access.  The client
+   * SHOULD NOT automatically repeat the request with the same
+   * credentials.  The client MAY repeat the request with new or different
+   * credentials.  However, a request might be forbidden for reasons
+   * unrelated to the credentials.
+   *
+   * An origin server that wishes to "hide" the current existence of a
+   * forbidden target resource MAY instead respond with a status code of
+   * 404 (Not Found).
+   */
+  403: "Forbidden",
+  /**
+   * The 404 (Not Found) status code indicates that the origin server did
+   * not find a current representation for the target resource or is not
+   * willing to disclose that one exists.  A 404 status code does not
+   * indicate whether this lack of representation is temporary or
+   * permanent; the 410 (Gone) status code is preferred over 404 if the
+   * origin server knows, presumably through some configurable means, that
+   * the condition is likely to be permanent.
+   *
+   * A 404 response is cacheable by default; i.e., unless otherwise
+   * indicated by the method definition or explicit cache controls (see
+   * Section 4.2.2 of [RFC7234]).
+   */
+  404: "Not Found",
+  /**
+   * The 405 (Method Not Allowed) status code indicates that the method
+   * received in the request-line is known by the origin server but not
+   * supported by the target resource.  The origin server MUST generate an
+   * Allow header field in a 405 response containing a list of the target
+   * resource's currently supported methods.
+   *
+   * A 405 response is cacheable by default; i.e., unless otherwise
+   * indicated by the method definition or explicit cache controls (see
+   * Section 4.2.2 of [RFC7234]).
+   */
+  405: "Method Not Allowed",
+  /**
+   * The 406 (Not Acceptable) status code indicates that the target
+   * resource does not have a current representation that would be
+   * acceptable to the user agent, according to the proactive negotiation
+   * header fields received in the request (Section 5.3), and the server
+   * is unwilling to supply a default representation.
+   *
+   * The server SHOULD generate a payload containing a list of available
+   * representation characteristics and corresponding resource identifiers
+   * from which the user or user agent can choose the one most
+   * appropriate.  A user agent MAY automatically select the most
+   * appropriate choice from that list.  However, this specification does
+   * not define any standard for such automatic selection, as described in
+   * Section 6.4.1 of [RFC7231]
+   */
+  406: "Not Acceptable",
+  /**
+   * Similar to 401 Unauthorized, but it indicates that the client needs to
+   * authenticate itself in order to use a proxy.
+   *
+   * The proxy MUST send a Proxy-Authenticate header field containing a
+   * challenge applicable to that proxy for the target resource. The client MAY
+   * repeat the request with a new or replaced Proxy-Authorization header field.
+   */
+  407: "Proxy Authentication Required",
+  /**
+   * The 408 (Request Timeout) status code indicates that the server did
+   * not receive a complete request message within the time that it was
+   * prepared to wait.  A server SHOULD send the "close" connection option
+   * (Section 6.1 of [RFC7230]) in the response, since 408 implies that
+   * the server has decided to close the connection rather than continue
+   * waiting.  If the client has an outstanding request in transit, the
+   * client MAY repeat that request on a new connection.
+   */
+  408: "Request Timeout",
+  /**
+   * The 409 (Conflict) status code indicates that the request could not
+   * be completed due to a conflict with the current state of the target
+   * resource.  This code is used in situations where the user might be
+   * able to resolve the conflict and resubmit the request.  The server
+   * SHOULD generate a payload that includes enough information for a user
+   * to recognize the source of the conflict.
+   *
+   * Conflicts are most likely to occur in response to a PUT request.  For
+   * example, if versioning were being used and the representation being
+   * PUT included changes to a resource that conflict with those made by
+   * an earlier (third-party) request, the origin server might use a 409
+   * response to indicate that it can't complete the request.  In this
+   * case, the response representation would likely contain information
+   * useful for merging the differences based on the revision history.
+   */
+  409: "Conflict",
+  /**
+   * The 410 (Gone) status code indicates that access to the target
+   * resource is no longer available at the origin server and that this
+   * condition is likely to be permanent.  If the origin server does not
+   * know, or has no facility to determine, whether or not the condition
+   * is permanent, the status code 404 (Not Found) ought to be used
+   * instead.
+   *
+   * The 410 response is primarily intended to assist the task of web
+   * maintenance by notifying the recipient that the resource is
+   * intentionally unavailable and that the server owners desire that
+   * remote links to that resource be removed.  Such an event is common
+   * for limited-time, promotional services and for resources belonging to
+   * individuals no longer associated with the origin server's site.  It
+   * is not necessary to mark all permanently unavailable resources as
+   * "gone" or to keep the mark for any length of time -- that is left to
+   * the discretion of the server owner.
+   *
+   * A 410 response is cacheable by default; i.e., unless otherwise
+   * indicated by the method definition or explicit cache controls (see
+   * Section 4.2.2 of [RFC7234]).
+   */
+  410: "Gone",
+  /**
+   * The 411 (Length Required) status code indicates that the server
+   * refuses to accept the request without a defined Content-Length
+   * (Section 3.3.2 of [RFC7230]).  The client MAY repeat the request if
+   * it adds a valid Content-Length header field containing the length of
+   * the message body in the request message.
+   */
+  411: "Length Required",
+  /**
+   * One or more conditions given in the request header fields evaluated to
+   * false when tested on the server.
+   *
+   * This response code allows the client to place preconditions on the current
+   * resource state (its current representations and metadata) and, thus,
+   * prevent the request method from being applied if the target resource is in
+   * an unexpected state.
+   */
+  412: "Precondition Failed",
+  /**
+   * The 413 (Payload Too Large) status code indicates that the server is
+   * refusing to process a request because the request payload is larger
+   * than the server is willing or able to process.  The server MAY close
+   * the connection to prevent the client from continuing the request.
+   *
+   * If the condition is temporary, the server SHOULD generate a
+   * Retry-After header field to indicate that it is temporary and after
+   * what time the client MAY try again.
+   */
+  413: "Payload Too Large",
+  /**
+   * The 414 (URI Too Long) status code indicates that the server is
+   * refusing to service the request because the request-target (Section
+   * 5.3 of [RFC7230]) is longer than the server is willing to interpret.
+   * This rare condition is only likely to occur when a client has
+   * improperly converted a POST request to a GET request with long query
+   * information, when the client has descended into a "black hole" of
+   * redirection (e.g., a redirected URI prefix that points to a suffix of
+   * itself) or when the server is under attack by a client attempting to
+   * exploit potential security holes.
+   *
+   * A 414 response is cacheable by default; i.e., unless otherwise
+   * indicated by the method definition or explicit cache controls (see
+   * Section 4.2.2 of [RFC7234]).
+   */
+  414: "Request-URI Too Long",
+  /**
+   * The 415 (Unsupported Media Type) status code indicates that the
+   * origin server is refusing to service the request because the payload
+   * is in a format not supported by this method on the target resource.
+   * The format problem might be due to the request's indicated
+   * Content-Type or Content-Encoding, or as a result of inspecting the
+   * data directly.
+   */
+  415: "Unsupported Media Type",
+  /**
+   * None of the ranges in the request's Range header field overlap the
+   * current extent of the selected resource or that the set of ranges
+   * requested has been rejected due to invalid ranges or an excessive request
+   * of small or overlapping ranges.
+   *
+   * For byte ranges, failing to overlap the current extent means that the
+   * first-byte-pos of all of the byte-range-spec values were greater than the
+   * current length of the selected representation. When this status code is
+   * generated in response to a byte-range request, the sender SHOULD generate
+   * a Content-Range header field specifying the current length of the selected
+   * representation
+   */
+  416: "Requested Range Not Satisfiable",
+  /**
+   * The 417 (Expectation Failed) status code indicates that the
+   * expectation given in the request's Expect header field
+   * (Section 5.1.1 of [RFC7231]) could not be met by at least one of the
+   * inbound servers.
+   */
+  417: "Expectation Failed",
+  /**
+   * Any attempt to brew coffee with a teapot should result in the error code
+   * "418 I'm a teapot". The resulting entity body MAY be short and stout.
+   */
+  418: "I'm a Teapot",
+  /**
+   * The request was directed at a server that is not able to produce a
+   * response. This can be sent by a server that is not configured to produce
+   * responses for the combination of scheme and authority that are included
+   * in the request URI.
+   *
+   * Clients receiving a 421 Misdirected Request response from a server MAY
+   * retry the request -- whether the request method is idempotent or
+   * not -- over a different connection. This is possible if a connection is
+   * reused or if an alternative service is selected ALT-SVC.
+   *
+   * This status code MUST NOT be generated by proxies.
+   *
+   * A 421 response is cacheable by default, i.e., unless otherwise indicated by
+   * the method definition or explicit cache controls
+   */
+  421: "Misdirected Request",
+  /**
+   * The server understands the content type of the request entity (hence a
+   * 415 Unsupported Media Type status code is inappropriate), and the syntax
+   * of the request entity is correct (thus a 400 Bad Request status code is
+   * inappropriate) but was unable to process the contained instructions.
+   *
+   * For example, this error condition may occur if an XML request body contains
+   * well-formed (i.e., syntactically correct), but semantically erroneous, XML
+   * instructions.
+   */
+  422: "Unprocessable Entity",
+  /**
+   * The source or destination resource of a method is locked.
+   *
+   * This response SHOULD contain an appropriate precondition or postcondition
+   * code, such as 'lock-token-submitted' or 'no-conflicting-lock'.
+   */
+  423: "Locked",
+  /**
+   * The method could not be performed on the resource because the requested
+   * action depended on another action and that action failed.
+   *
+   * For example, if a command in a PROPPATCH method fails, then, at minimum,
+   * the rest of the commands will also fail with 424 Failed Dependency.
+   */
+  424: "Failed Dependency",
+  /**
+   * The 426 (Upgrade Required) status code indicates that the server
+   * refuses to perform the request using the current protocol but might
+   * be willing to do so after the client upgrades to a different
+   * protocol.  The server MUST send an Upgrade header field in a 426
+   * response to indicate the required protocol(s) (Section 6.7 of
+   * [RFC7230]).
+   */
+  426: "Upgrade Required",
+  /**
+   * The origin server requires the request to be conditional.
+   *
+   * Its typical use is to avoid the "lost update" problem, where a client GETs
+   * a resource's state, modifies it, and PUTs it back to the server, when
+   * meanwhile a third party has modified the state on the server, leading
+   * to a conflict. By requiring requests to be conditional, the server can
+   * assure that clients are working with the correct copies.
+   *
+   * Responses using this status code SHOULD explain how to resubmit the request
+   * successfully.
+   *
+   * Responses with the 428 status code MUST NOT be stored by a cache.
+   */
+  428: "Precondition Required",
+  /**
+   * The user has sent too many requests in a given amount of time
+   * ("rate limiting").
+   *
+   * The response representations SHOULD include details explaining the
+   * condition, and MAY include a Retry-After header indicating how long to
+   * wait before making a new request.
+   *
+   * Responses with the 429 status code MUST NOT be stored by a cache.
+   */
+  429: "Too Many Requests",
+  /**
+   * The server is unwilling to process the request because its header fields
+   * are too large. The request MAY be resubmitted after reducing the size of
+   * the request header fields.
+   *
+   * It can be used both when the set of request header fields in total is too
+   * large, and when a single header field is at fault. In the latter case, the
+   * response representation SHOULD specify which header field was too large.
+   */
+  431: "Request Header Fields Too Large",
+  /**
+   * A non-standard status code used to instruct nginx to close the connection
+   * without sending a response to the client, most commonly used to deny
+   * malicious or malformed requests.
+   *
+   * This status code is not seen by the client, it only appears in nginx log
+   * files.
+   */
+  444: "Connection Closed Without Response",
+  /**
+   * The server is denying access to the resource as a consequence of a legal
+   * demand.
+   *
+   * The server in question might not be an origin server. This type of legal
+   * demand typically most directly affects the operations of ISPs and search
+   * engines.
+   *
+   * Responses using this status code SHOULD include an explanation, in the
+   * response body, of the details of the legal demand: the party making it,
+   * the applicable legislation or regulation, and what classes of person and
+   * resource it applies to.
+   *
+   * The use of the 451 status code implies neither the existence nor
+   * non-existence of the resource named in the request. That is to say, it is
+   * possible that if the legal demands were removed, a request for the
+   * resource still might not succeed.
+   *
+   * Note that in many cases clients can still access the denied resource by
+   * using technical countermeasures such as a VPN or the Tor network.
+   *
+   * A 451 response is cacheable by default; i.e., unless otherwise indicated
+   * by the method definition or explicit cache controls; see RFC7234.
+   */
+  451: "Unavailable For Legal Reasons",
+  /**
+   * A non-standard status code introduced by nginx for the case when a client
+   * closes the connection while nginx is processing the request.
+   */
+  499: "Client Closed Request",
+  /**
+   * The 500 (Internal Server Error) status code indicates that the server
+   * encountered an unexpected condition that prevented it from fulfilling
+   * the request.
+   */
+  500: "Internal Server Error",
+  /**
+   * The 501 (Not Implemented) status code indicates that the server does
+   * not support the functionality required to fulfill the request.  This
+   * is the appropriate response when the server does not recognize the
+   * request method and is not capable of supporting it for any resource.
+   *
+   * A 501 response is cacheable by default; i.e., unless otherwise
+   * indicated by the method definition or explicit cache controls (see
+   * Section 4.2.2 of [RFC7234]).
+   */
+  501: "Not Implemented",
+  /**
+   * The 502 (Bad Gateway) status code indicates that the server, while
+   * acting as a gateway or proxy, received an invalid response from an
+   * inbound server it accessed while attempting to fulfill the request.
+   */
+  502: "Bad Gateway",
+  /**
+   * The 503 (Service Unavailable) status code indicates that the server
+   * is currently unable to handle the request due to a temporary overload
+   * or scheduled maintenance, which will likely be alleviated after some
+   * delay.  The server MAY send a Retry-After header field
+   * (Section 7.1.3 of [RFC7231]) to suggest an appropriate amount of time for
+   * the client to wait before retrying the request.
+   */
+  503: "Service Unavailable",
+  /**
+   * The 504 (Gateway Timeout) status code indicates that the server,
+   *while acting as a gateway or proxy, did not receive a timely response
+   *from an upstream server it needed to access in order to complete the
+   *request.
+   */
+  504: "Gateway Timeout",
+  /**
+   * The 505 (HTTP Version Not Supported) status code indicates that the
+   *server does not support, or refuses to support, the major version of
+   *HTTP that was used in the request message.  The server is indicating
+   *that it is unable or unwilling to complete the request using the same
+   *major version as the client, as described in Section 2.6 of
+   *[RFC7230], other than with this error message.  The server SHOULD
+   *generate a representation for the 505 response that describes why
+   *that version is not supported and what other protocols are supported
+   *by that server.
+   */
+  505: "HTTP Version Not Supported",
+  /**
+   * The server has an internal configuration error: the chosen variant
+   * resource is configured to engage in transparent content negotiation
+   * itself, and is therefore not a proper end point in the negotiation
+   * process.
+   */
+  506: "Variant Also Negotiates",
+  /**
+   * The method could not be performed on the resource because the server is
+   * unable to store the representation needed to successfully complete the
+   * request.
+   *
+   * This condition is considered to be temporary. If the request that received
+   * this status code was the result of a user action, the request MUST NOT be
+   * repeated until it is requested by a separate user action.
+   */
+  507: "Insufficient Storage",
+  /**
+   * The server terminated an operation because it encountered an infinite loop
+   * while processing a request with "Depth: infinity". This status indicates
+   * that the entire operation failed.
+   */
+  508: "Loop Detected",
+  /**
+   * The policy for accessing the resource has not been met in the request. The
+   * server should send back all the information necessary for the client to
+   * issue an extended request.
+   *
+   * It is outside the scope of this specification to specify how the
+   * extensions inform the client.
+   *
+   * If the 510 response contains information about extensions that were not
+   * present in the initial request then the client MAY repeat the request if
+   * it has reason to believe it can fulfill the extension policy by modifying
+   * the request according to the information provided in the 510 response.
+   * Otherwise the client MAY present any entity included in the 510 response
+   * to the user, since that entity may include relevant diagnostic information.
+   */
+  510: "Not Extended",
+  /**
+   * The client needs to authenticate to gain network access.
+   *
+   * The response representation SHOULD contain a link to a resource that
+   * allows the user to submit credentials (e.g., with an HTML form).
+   *
+   * Note that the 511 response SHOULD NOT contain a challenge or the login
+   * interface itself, because browsers would show the login interface as being
+   * associated with the originally requested URL, which may cause confusion.
+   *
+   * The 511 status SHOULD NOT be generated by origin servers; it is intended
+   * for use by intercepting proxies that are interposed as a means of
+   * controlling access to the network.
+   *
+   * Responses with the 511 status code MUST NOT be stored by a cache.
+   */
+  511: "Network Authentication Required",
+  /**
+   * This status code is not specified in any RFCs, but is used by some HTTP
+   * proxies to signal a network connect timeout behind the proxy to a client
+   * in front of the proxy.
+   */
+  599: "Network Connect Timeout Error"
+};
+var isValidStatusCode = (code) => !!HTTPStatuses[code];
+var isInformational = (code) => code >= 100 && code < 200;
+var isSuccessful = (code) => code >= 200 && code < 300;
+var isRedirection = (code) => code >= 300 && code < 400;
+var isClientError = (code) => code >= 400 && code < 500;
+var isServerError = (code) => code >= 500;
+var getCodeForStatus = (status) => {
+  const clnStr = status.toLocaleLowerCase().trim();
+  const entry = Object.entries(HTTPStatuses).find(
+    (ent) => ent[1].toLowerCase() === clnStr
+  );
+  if (entry) return parseInt(entry[0]);
+  return null;
+};
+var httpStatusCodes_default = HTTPStatuses;
+
+// src/http/openApiV3Generator/openApiV3Generator.ts
+function toUpperCase(str) {
+  return str.charAt(0).toUpperCase() + str.slice(1);
+}
+function transformBasePath(basePath) {
+  if (basePath.startsWith("/")) {
+    return toUpperCase(basePath.slice(1));
+  }
+  return `/${basePath}`;
+}
+function swaggerDocument(port, tags, paths) {
+  return {
+    openapi: "3.1.0",
+    info: {
+      title: process.env.API_TITLE || "",
+      version: process.env.VERSION || "1.0.0"
+    },
+    components: {
+      securitySchemes: {
+        bearer: {
+          type: "http",
+          scheme: "bearer",
+          bearerFormat: "JWT"
+        }
+      }
+    },
+    tags,
+    servers: [
+      {
+        url: `http://localhost:${port}`
+      }
+    ],
+    paths
+  };
+}
+function contentResolver(schemaValidator, body) {
+  const bodySpec = schemaValidator.openapi(body);
+  return body === schemaValidator.string ? {
+    "plain/text": {
+      schema: bodySpec
+    }
+  } : {
+    "application/json": {
+      schema: bodySpec
+    }
+  };
+}
+function generateSwaggerDocument(schemaValidator, port, routers) {
+  const tags = [];
+  const paths = {};
+  routers.flat(Infinity).forEach((router) => {
+    const controllerName = transformBasePath(router.basePath);
+    tags.push({
+      name: controllerName,
+      description: `${controllerName} Operations`
+    });
+    router.routes.forEach((route) => {
+      const fullPath = `${router.basePath}${route.path === "/" ? "" : route.path}`.replace(
+        /:(\w+)/g,
+        "{$1}"
+      );
+      if (!paths[fullPath]) {
+        paths[fullPath] = {};
+      }
+      const { name, summary, query, requestHeaders } = route.contractDetails;
+      const responses = {};
+      for (const key in route.contractDetails.responses) {
+        responses[key] = {
+          description: httpStatusCodes_default[key],
+          content: contentResolver(
+            schemaValidator,
+            route.contractDetails.responses[key]
+          )
+        };
+      }
+      const pathItemObject = {
+        tags: [controllerName],
+        summary: `${name}: ${summary}`,
+        parameters: [],
+        responses
+      };
+      if (route.contractDetails.params) {
+        for (const key in route.contractDetails.params) {
+          pathItemObject.parameters?.push({
+            name: key,
+            in: "path"
+          });
+        }
+      }
+      const body = route.contractDetails.body;
+      if (body) {
+        pathItemObject.requestBody = {
+          required: true,
+          content: contentResolver(schemaValidator, body)
+        };
+      }
+      if (requestHeaders) {
+        for (const key in requestHeaders) {
+          pathItemObject.parameters?.push({
+            name: key,
+            in: "header"
+          });
+        }
+      }
+      if (query) {
+        for (const key in query) {
+          pathItemObject.parameters?.push({
+            name: key,
+            in: "query"
+          });
+        }
+      }
+      if (route.contractDetails.auth) {
+        responses[401] = {
+          description: httpStatusCodes_default[401],
+          content: contentResolver(schemaValidator, schemaValidator.string)
+        };
+        responses[403] = {
+          description: httpStatusCodes_default[403],
+          content: contentResolver(schemaValidator, schemaValidator.string)
+        };
+        if (route.contractDetails.auth.method === "jwt") {
+          pathItemObject.security = [
+            {
+              bearer: Array.from(
+                route.contractDetails.auth.allowedPermissions?.values() || []
+              )
+            }
+          ];
+        }
+      }
+      if (route.method !== "middleware") {
+        paths[fullPath][route.method] = pathItemObject;
+      }
+    });
+  });
+  return swaggerDocument(port, tags, paths);
+}
+
+// src/http/middleware/response/parse.middleware.ts
+function parse2(req, res, next) {
+  console.debug("[MIDDLEWARE] parseResponse started");
+  const { headers, responses } = res.responseSchemas;
+  const parsedResponse = req.schemaValidator.parse(
+    responses?.[res.statusCode],
+    res.bodyData
+  );
+  const parsedHeaders = req.schemaValidator.parse(
+    headers ?? req.schemaValidator.unknown,
+    res.getHeaders()
+  );
+  const parseErrors = [];
+  if (!parsedHeaders.ok) {
+    parseErrors.push(
+      `${parsedHeaders.error ? `Header ${parsedHeaders.error}` : ""}`
+    );
+  }
+  if (!parsedResponse.ok) {
+    parseErrors.push(
+      `${parsedResponse.error ? `Response ${parsedResponse.error}` : ""}`
+    );
+  }
+  if (parseErrors.length > 0) {
+    switch (req.contractDetails.options?.responseValidation) {
+      default:
+      case "error":
+        next?.(new Error(`Invalid response:
+${parseErrors.join("\n\n")}`));
+        break;
+      case "warning":
+        console.warn(`Invalid response:
+${parseErrors.join("\n\n")}`);
+        break;
+      case "none":
+        break;
+    }
+  }
+  next?.();
+}
+
+// src/http/utils/enrichExpressLikeSend.ts
+function enrichExpressLikeSend(instance, req, res, originalSend, data, shouldEnrich) {
+  let parseErrorSent;
+  if (shouldEnrich) {
+    if (res.statusCode === 404) {
+      res.status(404);
+      originalSend.call(instance, "Not Found");
+    }
+    parse2(req, res, (err) => {
+      if (err) {
+        let errorString = err.message;
+        if (res.locals.errorMessage) {
+          errorString += `
+------------------
+${res.locals.errorMessage}`;
+        }
+        res.status(500);
+        originalSend.call(instance, errorString);
+        parseErrorSent = true;
+      }
+    });
+  }
+  if (!parseErrorSent) {
+    originalSend.call(instance, data);
+  }
+}
+export {
+  ForklaunchExpressLikeApplication,
+  ForklaunchExpressLikeRouter,
+  HTTPStatuses,
+  delete_,
+  enrichExpressLikeSend,
+  generateSwaggerDocument,
+  get,
+  getCodeForStatus,
+  head,
+  isClientError,
+  isForklaunchRouter,
+  isInformational,
+  isRedirection,
+  isServerError,
+  isSuccessful,
+  isValidStatusCode,
+  middleware,
+  options,
+  patch,
+  post,
+  put,
+  trace,
+  typedHandler
+};