in the screenshot you can see that it is not called at all, because the pages tail has the api/v1/pi

FF0rce in the screenshot you can see that it is not called at all, because the pages ta...

H

Hello, I’m Allie!•2/23/24, 7:39 PM

Yeah, so something else is happening. What is the route for your Worker?

F

F0rceOP•2/23/24, 7:39 PM

route = { pattern = "dashboard.ruxiom.dev/api/*", zone_name = "ruxiom.dev" }

route = { pattern = "dashboard.ruxiom.dev/api/*", zone_name = "ruxiom.dev" }

route = { pattern = "dashboard.ruxiom.dev/api/*", zone_name = "ruxiom.dev" }

route = { pattern = "dashboard.ruxiom.dev/api/*", zone_name = "ruxiom.dev" }

F

F0rceOP•2/23/24, 7:41 PM

and the Page has a custom domain pointing to

dashboard.ruxiom.dev

dashboard.ruxiom.dev

F

F0rceOP•2/23/24, 7:47 PM

absolute url with excluding does not work...

S

Simciutoja•2/23/24, 7:53 PM

0:23:57.383    Deploying your site to Cloudflare's global network...
20:24:00.014    Uploading... (0/26)
20:24:00.742    Uploading... (9/26)
20:24:00.898    Uploading... (17/26)
20:24:01.763    Uploading... (26/26)
20:24:01.763    ✨ Success! Uploaded 26 files (2.31 sec)
20:24:01.763    
20:24:02.295    ✨ Upload complete!
20:24:04.409    Success: Assets published!
20:24:05.495    Success: Your site was deployed!

0:23:57.383    Deploying your site to Cloudflare's global network...
20:24:00.014    Uploading... (0/26)
20:24:00.742    Uploading... (9/26)
20:24:00.898    Uploading... (17/26)
20:24:01.763    Uploading... (26/26)
20:24:01.763    ✨ Success! Uploaded 26 files (2.31 sec)
20:24:01.763    
20:24:02.295    ✨ Upload complete!
20:24:04.409    Success: Assets published!
20:24:05.495    Success: Your site was deployed!

0:23:57.383    Deploying your site to Cloudflare's global network...
20:24:00.014    Uploading... (0/26)
20:24:00.742    Uploading... (9/26)
20:24:00.898    Uploading... (17/26)
20:24:01.763    Uploading... (26/26)
20:24:01.763    ✨ Success! Uploaded 26 files (2.31 sec)
20:24:01.763    
20:24:02.295    ✨ Upload complete!
20:24:04.409    Success: Assets published!
20:24:05.495    Success: Your site was deployed!

0:23:57.383    Deploying your site to Cloudflare's global network...
20:24:00.014    Uploading... (0/26)
20:24:00.742    Uploading... (9/26)
20:24:00.898    Uploading... (17/26)
20:24:01.763    Uploading... (26/26)
20:24:01.763    ✨ Success! Uploaded 26 files (2.31 sec)
20:24:01.763    
20:24:02.295    ✨ Upload complete!
20:24:04.409    Success: Assets published!
20:24:05.495    Success: Your site was deployed!

S

Simciutoja•2/23/24, 7:54 PM

could someone help? I'v trying to upload strapi.

S

Simciutoja•2/23/24, 7:54 PM

on localhost its works but unfortunetly there not.

F

F0rceOP•2/23/24, 8:14 PM

the wierd thing is that a normal request (from bruno, local, or the browser itself) succeedes. only the sort of "subrequest" to an worker route from a cloudflare page is not working as expected (or by design)

F

F0rceOP•2/23/24, 9:00 PM

ok I was able to finally sort it out. But this seems like a super hacky workaround, there has to be a way to do without my current doings..... (worker sites had the exact use-case I am looking for right now).

Basically in Astro I created an

/api/[...request].js

/api/[...request].js

route (which is an api route) in my

pages

pages

folder.
The content is pretty simple:

export async function GET({ params }) {
  const backendRequest = await fetch(
    "https://dashboard.ruxiom.dev/api/" + params.request,
    {
      headers: {
        "CF-Access-Client-Id": "something.access",
        "CF-Access-Client-Secret":
          "something different",
      },
    }
  );

  return backendRequest.clone();
}

export async function GET({ params }) {
  const backendRequest = await fetch(
    "https://dashboard.ruxiom.dev/api/" + params.request,
    {
      headers: {
        "CF-Access-Client-Id": "something.access",
        "CF-Access-Client-Secret":
          "something different",
      },
    }
  );

  return backendRequest.clone();
}

export async function GET({ params }) {
  const backendRequest = await fetch(
    "https://dashboard.ruxiom.dev/api/" + params.request,
    {
      headers: {
        "CF-Access-Client-Id": "something.access",
        "CF-Access-Client-Secret":
          "something different",
      },
    }
  );

  return backendRequest.clone();
}

export async function GET({ params }) {
  const backendRequest = await fetch(
    "https://dashboard.ruxiom.dev/api/" + params.request,
    {
      headers: {
        "CF-Access-Client-Id": "something.access",
        "CF-Access-Client-Secret":
          "something different",
      },
    }
  );

  return backendRequest.clone();
}

As you can see I had to add an additional Service Auth Include Rule in our Zero Trust Dashboard, without it I get the error that I am not allowed to view that endpoint.

This seems absolutely ridicoulus, it really does...

F

F0rceOP•2/23/24, 9:00 PM

cc @Hello, I’m Allie!

F

F0rceOP•2/23/24, 9:05 PM

and in my Astro test page which should load some data from the backend it looks the following:

import "@/styles/globals.css";
import { cn } from "@/lib/utils";

let message = "Hello World";
try {
  const api = await fetch("https://dashboard.ruxiom.dev/api/v1/ping");
  message = await api.text();
} catch (error) {
  console.log(error);
  message = "Error or nothing found :(";
}

import "@/styles/globals.css";
import { cn } from "@/lib/utils";

let message = "Hello World";
try {
  const api = await fetch("https://dashboard.ruxiom.dev/api/v1/ping");
  message = await api.text();
} catch (error) {
  console.log(error);
  message = "Error or nothing found :(";
}

import "@/styles/globals.css";
import { cn } from "@/lib/utils";

let message = "Hello World";
try {
  const api = await fetch("https://dashboard.ruxiom.dev/api/v1/ping");
  message = await api.text();
} catch (error) {
  console.log(error);
  message = "Error or nothing found :(";
}

import "@/styles/globals.css";
import { cn } from "@/lib/utils";

let message = "Hello World";
try {
  const api = await fetch("https://dashboard.ruxiom.dev/api/v1/ping");
  message = await api.text();
} catch (error) {
  console.log(error);
  message = "Error or nothing found :(";
}

This is a cross-reference doing something twice loop-hole and I really dont think this is intentional behaviour........

F

F0rceOP•2/23/24, 9:08 PM

I just see the problem with invocations at the end... the page is invoced twice (once for the page and once for the "proxy" api call). The worker is invoced once (which is correct). But when making a lot of request to the backend to load some sort of data to display in the ui, thats where the invocation count will go up

F

F0rceOP•2/23/24, 9:21 PM

request to page --> pages calls internal api --> pages calls external api --> page loads

1

1million7393•2/24/24, 3:31 PM

hello, i deploy my website page on cloud flare page, but when i want input my sitemap on google search console it say error couln't fetch

1

1million7393•2/24/24, 3:31 PM

how to solve this problem?

FF0rce and in my Astro test page which should load some data from the backend it looks ...

F

F0rceOP•2/24/24, 7:05 PM

im still super lost here, any direction would be so much appreciated...

Bbinsarsempak hello guys where i can report abuse ?

C

Cyb3r-Jak3•2/25/24, 2:14 PM

?abuse

F

Flare•2/25/24, 2:14 PM

If you feel that a site is engaging in illegal or inappropriate activities, you can submit an abuse report at https://abuse.cloudflare.com/. The Trust and Safety team will review the details and reply if appropriate. You can also report the site to your relevant local authorities. Reports cannot be filed via Discord or with individual employees or Champs.

Kknutern Having some issues with added robots.txt for my CF page, deployed through github...

T

tcurdt•2/25/24, 10:19 PM

Did you find anything? I am having a similar issue.

T

tcurdt•2/25/24, 10:19 PM

For any error page it just shows

instead

T

tcurdt•2/25/24, 10:20 PM

And it does not even return my

robots.txt

robots.txt

on the

pages.dev

pages.dev

for some reason.

T

tcurdt•2/25/24, 10:23 PM

Hm ... but if it was caching it should return the previous version of the

robots.txt

robots.txt

. That's all a little weird.

T

tcurdt•2/25/24, 10:24 PM

 $ cat _site/robots.txt                                    
user-agent: *
disallow: /legal
disallow: /privacy
disallow: /cv
disallow: /links%                                                                                                                                   
$ curl https://site-torstencurdt-com.pages.dev/robots.txt
<html lang="en-US">
<head>

<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
...

$ curl https://torstencurdt.com/robots.txt
<html lang="en-US">
<head>

<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
...

 $ cat _site/robots.txt                                    
user-agent: *
disallow: /legal
disallow: /privacy
disallow: /cv
disallow: /links%                                                                                                                                   
$ curl https://site-torstencurdt-com.pages.dev/robots.txt
<html lang="en-US">
<head>

<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
...

$ curl https://torstencurdt.com/robots.txt
<html lang="en-US">
<head>

<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
...

 $ cat _site/robots.txt                                    
user-agent: *
disallow: /legal
disallow: /privacy
disallow: /cv
disallow: /links%                                                                                                                                   
$ curl https://site-torstencurdt-com.pages.dev/robots.txt
<html lang="en-US">
<head>

<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
...

$ curl https://torstencurdt.com/robots.txt
<html lang="en-US">
<head>

<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
...

 $ cat _site/robots.txt                                    
user-agent: *
disallow: /legal
disallow: /privacy
disallow: /cv
disallow: /links%                                                                                                                                   
$ curl https://site-torstencurdt-com.pages.dev/robots.txt
<html lang="en-US">
<head>

<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
...

$ curl https://torstencurdt.com/robots.txt
<html lang="en-US">
<head>

<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
...

T

tcurdt•2/25/24, 10:25 PM

not sure what I could be missing

T

tcurdt•2/25/24, 10:27 PM

I just switched to pages.
Before I had a typo and it was just

robot.txt

robot.txt

.
So the question is how would any caching come from?

T

tcurdt•2/25/24, 10:28 PM

Idea - maybe I purge the site cache. Just for fun.

T

tcurdt•2/25/24, 10:29 PM

Na, the purge didn't help.

T

tcurdt•2/25/24, 10:32 PM

it just keeps caching

T

tcurdt•2/25/24, 10:33 PM

that's when all this serverless stuff brings back the pain

T

tcurdt•2/25/24, 10:33 PM

well, I guess I'll check in a few hours again

T

tcurdt•2/25/24, 10:40 PM

It was just me being stupid

... robots.txt works now

T

tcurdt•2/25/24, 10:40 PM

but returning

for a 404 is not great

T

tcurdt•2/25/24, 10:40 PM

and I didn't find where to change that yet

W

Walshy•2/25/24, 10:40 PM

https://developers.cloudflare.com/pages/configuration/serving-pages/#single-page-application-spa-rendering

W

Walshy•2/25/24, 10:41 PM

If your project does not include a top-level 404.html file, Pages assumes that you are deploying a single-page application. This includes frameworks like React, Vue, and Angular. Pages’ default single-page application behavior matches all incoming paths to the root (/)

W

Walshy•2/25/24, 10:47 PM

as for custom domain caching, that's independant of Pages' cache. Pages does not mess with your zone cache.

So, by default everything listed (https://developers.cloudflare.com/cache/concepts/default-cache-behavior/#default-cached-file-extensions) is cached for a while. Purging zone cache will clear it
Additionally, I'd recommend skipping cache for Pages projects and let Pages handle it

T

tcurdt•2/25/24, 10:49 PM

Absolutely not where I would have found it in the docs. Thanks for the pointer!

FF0rce ok I was able to finally sort it out. But this seems like a super hacky workarou...

F

F0rceOP•2/26/24, 1:02 PM

still stuck on this and cant get this out of my head...

in the screenshot you can see that it is not called at all, because the pages tail has the api/v1/pi

Similar Threads

Similar Threads

Similar Threads