Look into type mismatch error during request handling.

[danfuzz]

Describe the bug

A short summary of the problem.

To reproduce

Steps to reproduce the problem:

Unclear. This was observed in production.

Expected behavior

No exception.

Actual behavior

Exceptions like this (excerpt of process.json file):

    "problems": [
      {
        "type": "unhandledRejection",
        "problem": {
          "@Error": {
            "message": "Must be of type `string`.",
            "stack": [
              {
                "name": "MustBe.string",
                "file": "file:///home/milk-user/lib/lactoserv/lib/code/node_modules/@this/typey/export/MustBe.js",
                "line": 278,
                "col": 13
              },
              {
                "name": "new RequestContext",
                "file": "file:///home/milk-user/lib/lactoserv/lib/code/node_modules/@this/net-util/export/RequestContext.js",
                "line": 64,
                "col": 14
              },
              {
                "name": "HttpWrangler._prot_incomingRequest",
                "file": "file:///home/milk-user/lib/lactoserv/lib/code/node_modules/@this/net-protocol/export/ProtocolWrangler.js",
                "line": 341,
                "col": 28
              },
              {
                "name": "Server.<anonymous>",
                "file": "file:///home/milk-user/lib/lactoserv/lib/code/node_modules/@this/net-protocol/private/HttpWrangler.js",
                "line": 26,
                "col": 44
              },

Environment

• OS: Amazon Linux 2023
• Node: 20
• Browser: n/a

[danfuzz]

This should be fixed by PR #443.