Handle static routes in SSR-configured Astro applications

[Lms24]

Description

This came up internally in Slack. There are cases where users configure their Astro app as server (i.e. SSR) but explicitly set some pages as static pages (i.e. opt out of SSR). Our Astro middleware is injected if we find a server-configuration.

Now in case of requests being made to static pages, our middleware accesses properties in the middleware context that should only be accessed in SSR routes. As a result, the server logs warnings:

`Astro.request.headers` is unavailable in "static" output mode, and in perendered pages within "hybrid" and "server" output modes.

We need to somehow find a flag to check in the middleware if the route we’re accessing is static vs. SSR. And if static, we bail and don’t touch the headers

[pawelgrzybek]

Hi, I encountered this issue as well. No matter if the output config is server or hybrid, when it encounters a statically rendered page, it logs…

`Astro.request.headers` is unavailable in "static" output mode, and in prerendered pages within "hybrid" and "server" output modes. If you need access to request headers, make sure that `output` is configured as either `"server"` or `output: "hybrid"` in your config file, and that the page accessing the headers is rendered on-demand.

It is especially annoying in case when the page is mostly static, with a very few exceptions of server side rendered output (hybrid mode).

[Lms24]

yeah, we currently treat hybrid and server in the same way. I'll put this on my todo list for this week but can't make promises because we're pretty much depending on what Astro gives us to differentiate the configuration on a route level.