#Is there a way to stop eliminate 404 errors from Randomly generated URLs

9 messages · Page 1 of 1 (latest)

frail dock
#

..., turing into Edge function calls on Netify?

iron vigilBOT
#

Hi @frail dock. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Astro’s docs don’t describe a way to globally prevent random 404 URLs from ever touching Netlify Functions/Edge Functions, but they do show how 404s are normally handled and where Edge Functions get involved.

Key points from the docs:

  • When you enable edgeMiddleware: true in the Netlify adapter, every request (including static assets, prerendered pages, and on‑demand pages) runs through a Netlify Edge Function that executes your Astro middleware. [Netlify usage]
  • If a request doesn’t match any Astro route, app.match(request) returns null and your adapter can return a 404 Response directly instead of rendering anything. [routeData]

So, within the limits of the docs:

  1. If you don’t need Edge middleware for everything, you can disable it so that random 404s don’t go through an Edge Function:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify';

export default defineConfig({
  adapter: netlify({
    edgeMiddleware: false, // or just omit this option
  }),
});

    With edgeMiddleware off, only your on‑demand (SSR) routes will hit Netlify Functions; static 404s will be served as normal static responses. [Netlify usage]

  2. At the adapter level, the recommended pattern is to check routing first and return a 404 Response if nothing matches, instead of trying to render:

    const routeData = app.match(request);
if (routeData) {
  return app.render(request, { routeData });
} else {
  // adapter-specific 404 response
  return new Response('Not found', { status: 404 });
}
#

This still involves a function invocation, but it avoids any extra work beyond a minimal 404. [routeData]

The knowledge sources do not explicitly document a Netlify‑specific switch that says “never invoke any function for unknown/random URLs”; they only show how to configure Edge middleware and how to return 404s efficiently from the adapter.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@frail dock Kapa.ai is still learning and improving, please let me know how I did by reacting below.

frail dock
#

Do redirects use the edge middleware?

#

@iron vigil Do redirects use the edge middleware?

iron vigilBOT
#

Let me check the knowledge base for you again. One moment! :books:

#

The knowledge sources do not explicitly state whether Astro’s own redirects (from redirects config or Astro.redirect()) automatically run through Netlify Edge middleware.

What is documented:

  • When you enable edgeMiddleware: true in the Netlify adapter, “an edge function will execute your middleware code for all requests including static assets, prerendered pages, and on-demand rendered pages.” [Netlify usage]
  • That description strongly implies that any request hitting your Astro app (including ones that end up being redirects) will first go through the Edge middleware when edgeMiddleware is enabled, but the docs do not call out redirects as a special case.

So, based on the docs:

  • With edgeMiddleware: true, your middleware runs for all incoming requests; if a request then results in a redirect (via config or Astro.redirect()), that redirect happens after middleware has already run. [Netlify usage; Routing redirects]
  • There is no documented way to have redirects bypass Edge middleware once edgeMiddleware is enabled.

Because the docs never state this behavior explicitly for redirects, there is some uncertainty, but the “all requests” wording is the only guidance available.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: