Handling malformed requests in adapters

[brettdh]

I've been noticing scanner traffic hitting my Remix app, which includes malformed requests like those described here: wingleung/remix-aws#44

Some of these don't even make it my Remix app code, which has me wondering: are there established patterns for how adapter authors should handle malformed requests? This adapter is pretty thin; it creates a URL and a Request, then passes the Request to createRequestHandler (part of @remix-run/node). Of course, if creating either of these fails, we never get to Remix.

Is there a "best practice" here for allowing the Remix app, rather than the adapter, to handle malformed requests, or is each adapter author kind of on their own there?

[brettdh]

Here's my current attempt at handing this in the adapter: wingleung/remix-aws#44 (comment)