Cloudflare Pages: _redirects Rule to Pages Function Not Invoking Function (Leads to Nuxt 404)
Original message was deleted
KHi team, I'm having an issue with a
Setup:
_redirectsSetup:
- Nuxt 3 App: Deployed to Cloudflare Pages (
).ssr: false - Goal: Use a Pages Function to act as a proxy to our backend API for serving OG meta tags for specific share URLs.
public/_redirectsfile content:- Pages Function: Located at
functions/api/internal-og-proxy/[uuid].ts. This function fetches HTML from our backend API (https://api.grepit.app/s/preview/:uuid) and returns it. - Cloudflare Pages Dashboard:
- Confirms the redirect rule above is active and valid for the deployment.
- Shows correct "Routing configuration" and "Invocation routes" for the
/api/internal-og-proxy/:uuidfunction path.
- When accessing the intended user-facing URL (e.g.,
https://grepit.app/s/SOME_VALID_UUID/preview):- We receive a
404 Not Foundresponse. - The content served is our Nuxt app's client-side 404 page.
- Critically, the Cloudflare Pages Function real-time logs show NO INVOCATION for the
internal-og-proxyfunction.
- We receive a
KDiagnostics Done:
The Pages Function itself is deployed and working correctly when called via its direct path (
Is there any known reason why an active
Thanks!
- **Direct Function Call Test:**
- Accessing the function directly (e.g.,
https://grepit.app/api/internal-og-proxy/SOME_VALID_UUID) WORKS perfectly. - It returns
HTTP/2 200 OKwith the expectedtext/htmlcontent from our backend API. - The Cloudflare Pages Function real-time logs DO show successful invocation and execution for this direct call.
- Accessing the function directly (e.g.,
- **`_redirects` Rule Parsing:**
- The Cloudflare deployment logs explicitly state "Parsed 1 valid redirect rule."
- The Cloudflare dashboard shows the rule
/s/:uuid/preview /api/internal-og-proxy/:uuid 200as active.
- **Hardcoded `_redirects` Test (No Change):**
- Temporarily changing the
rule to use a hardcoded UUID instead of the_redirects:uuidplaceholder (e.g.,/s/ACTUAL_UUID/preview /api/internal-og-proxy/ACTUAL_UUID 200) still resulted in the same 404 for the/previewURL and no function invocation.
- Temporarily changing the
The Pages Function itself is deployed and working correctly when called via its direct path (
/api/internal-og-proxy/:uuid). The _redirectsIs there any known reason why an active
_redirectsThanks!
K@Cloudflare (Dev) Any help here?
