[Bug?]: cloudflare-pages in production does not have 404 status code for [...404] route

[huseeiin]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

200

Expected behavior 🤔

404

Steps to reproduce 🕹

import { Title } from "@solidjs/meta";
import { HttpStatusCode } from "@solidjs/start";

export default function NotFound() {
  return (
    <>
      <Title>Not Found</Title>
      <HttpStatusCode code={404} />
      <div>Not Found</div>
    </>
  );
}

go to http://localhost:8788/url-that-does-not-exist
you'll see 404 status code in wrangler pages dev but not in production

Context 🔦

this bug doesn't occur in cloudflare-worker preset, only cloudflare-pages

Your environment 🌎

[huseeiin]

HttpStatusCode does not work unless you set mode to "async"

[sabercoy]

yup, I had to do this

import { Title } from '@solidjs/meta'
import { HttpStatusCode } from '@solidjs/start'
import { getRequestEvent, isServer } from 'solid-js/web'

export default function() {
  if (isServer) {
    const event = getRequestEvent()
    if (event) event.response.status = 404
  }

  return (
    <main>
      <Title>Not Found</Title>
      {/* <HttpStatusCode code={404} text='testing' /> */}
      <h1>Page Not Found</h1>
    </main>
  )
}

[birkskyum]

Retested on @solidjs/start@2.0.0-rc.3 with a [...404] route using <HttpStatusCode code={404} />, in default stream mode (no mode: "async"):

• Node build: 404 ✅
• cloudflare_module + wrangler dev: 404 ✅
• cloudflare_pages + wrangler pages dev: 404 ✅

Also verified the harder case where the status is set only after a deferStream: true resource resolves, which returns 404 as well.

The root cause was the streaming path, not Cloudflare: in v2 event.response is h3's event.res directly, and #2231 defers the handler response until the stream shell payload is produced, so the status set during SSR lands on the outgoing response. Note that the v1 cloudflare-pages Nitro preset no longer exists in the v2 stack; the recommended Cloudflare target is now Workers with static assets.

Closing as fixed in v2. The original report was production-only, so if anyone still sees a 200 on a deployed Pages project running rc.3 or later, please comment and we'll reopen.