Unable to catch bad requests about expressly HOT 3 CLOSED

Hi @aivong3, I'll close this issue now, noting that the behaviour is limited to non-RFC3986 compliant paths.

from expressly.

Hi @aivong3,

This looks like a runtime issue, rather than an expressly issue.

Taking the following Compute application, which should return OK (HTTP 200) on any route, and running curl -svo /dev/null "http://127.0.0.1:7676/<", produces the same 400 Bad Request response:

/// <reference types="@fastly/js-compute" />

addEventListener("fetch", (event) => event.respondWith(handleRequest(event)));

async function handleRequest(event) {
  console.log(`Request received in Compute: ${event.request.method} ${event.request.url}`)
  return new Response("OK", { status: 200 });
}

I am therefore redirecting this issue to the runtime team – CC @JakeChampion

I suspect it's something to do with the < (non-RFC3986 compliant path) in particular.

Running the following:

curl -svo /dev/null  "http://127.0.0.1:7676/not-a-route"
curl -svo /dev/null  "https://quickly-sure-caribou.edgecompute.app/not-a-route"

In expressly:

import { Router } from "@fastly/expressly";

const router = new Router();

router.use((req, res) => {
  console.log(`Request received: ${req.method} ${req.url}`);
});

router.get("/", async (req, res) => {
  return res.send("Hello world!");
});

router.use((err, req, res) => {
  console.error(err);
  res.withStatus(500).send(`Uh-oh! Something went wrong: ${err.message}`);
});

router.listen();

Results in the expected logs and 500 error.

from expressly.

Hi @doramatadora,

Thanks for taking a look! It would be nice to have the flexibility to handle these bad requests in a custom way like we can for the other errors. Will see if this is possible with the runtime team

from expressly.