Hey functions team, I'm trying to deploy a simple hello world function. I am using nuxt.js and juxt

Bbllchmbrs Hey functions team, I'm trying to deploy a simple hello world function. I am usi...

B

bllchmbrsOP•8/2/23, 3:48 AM

I think I found a bug: https://github.com/cloudflare/workers-sdk/issues/3401
reported there.

GitHub

Workers not being deployed for Nuxt 3 projects · Issue #3401 · clou...

I would really like some clarity regarding the following: (Edit: Forgot to add that I intended to ask @luc122c about this - thanks for any input!) I am a bit confused by this issue: Is the intended...

C

Cretezy•8/2/23, 4:11 AM

How does Cloudflare Pages Functions behave when importing files in the rest of the project (under the root directory, but not

functions

functions

) which import npm packages? (e.g.

functions/index.ts

functions/index.ts

functions/index.ts

functions/index.ts ->

src/schema.ts

src/schema.ts

src/schema.ts

src/schema.ts ->

zod

zod

)

CCretezy How does Cloudflare Pages Functions behave when importing files in the rest of t...

H

Hello, I’m Allie!•8/2/23, 4:23 AM

Should work fine

Original message was deleted

B

bllchmbrsOP•8/2/23, 12:31 PM

Thanks for this guidance, but how do I move my functions to nuxt's server endpoint? Is this inside of the

/server

/server

/server

/serverdirectory? I've spent hours pouring over docs and I can't figure out how to do it. I'd be happy to write / contribute a documentation snippet or just include it in that github for others, I just don't know what to do.

B

bllchmbrsOP•8/2/23, 1:50 PM

I don't understand enough about the expectations of cloudflare functions to do any of that work confidently. It's not covered in the CF pages documentation and kind of goes against what's in the getting started guide. It feels like a hack but I just don't know enough about the systems to spend time on it. I think functions probably aren't for me.

B

bllchmbrsOP•8/2/23, 4:29 PM

will give this a try!

B

bllchmbrsOP•8/2/23, 4:29 PM

Thanks

E

EvanPiro•8/3/23, 7:29 PM

Is there are an equivalent to

google-auth-library

google-auth-library

google-auth-library

google-auth-library that will work in a function?

Original message was deleted

A

Asatsuki•8/3/23, 11:15 PM

so i tried not using a functions folder completely, and just having /server/api/hello.ts that just returns 'hello'. in nuxt.config.ts i set

nitro: {
     preset: 'cloudflare-pages'
},

nitro: {
     preset: 'cloudflare-pages'
},

nitro: {
     preset: 'cloudflare-pages'
},

nitro: {
     preset: 'cloudflare-pages'
},

but it still doesn't work. do you happen to know if i am missing something?

A

Asatsuki•8/4/23, 12:34 AM

ah it's because i'm using nuxt generate, which is for SSG sites, and that means i can't use the /server stuff at all

S

Shivam•8/5/23, 7:32 AM

I am using middleware in

/functions

/functions

to secure some pages. But when the url has double slashes

//

//

, wrangler doesn't run the middleware for the url.

I have replicated the issue in a minimal repo here – https://github.com/Shivam010/cloudflare-double-slashes-issue

I have also asked help on wrangler-sdk repo https://github.com/cloudflare/workers-sdk/issues/3677 but it feels like they are overburdened with other issues.

Am I missing something here? or is this an actual issue?

GitHub

GitHub - Shivam010/cloudflare-double-slashes-issue

Contribute to Shivam010/cloudflare-double-slashes-issue development by creating an account on GitHub.

GitHub

🐛 BUG: In some cases, urls with double slashes don't invoke Pages F...

Which Cloudflare product(s) does this pertain to? Pages What version(s) of the tool(s) are you using? latest What version of Node are you using? 20.1.0 What operating system are you using? Mac Desc...

S

Shivam•8/5/23, 7:35 AM

More description on the issue
It's replicated in https://github.com/Shivam010/cloudflare-double-slashes-issue

There's a middleware in

/functions/secure

/functions/secure

directory to be applied on all routes of

/secure

/secure

.

And the

/out/secure

/out/secure

/out/secure

/out/secure directory contains a file

one.html

one.html

one.html

one.html which should be served at

/secure/one

/secure/one

(but first the middleware needs to be invoked)

The issue is...

The middleware is properly invoked on

/secure/one

/secure/one

route but not on the

//secure/one

//secure/one

, whenever someone uses a double slash before the middleware directory, wrangler doesn't run the middleware and instead directly serve the pages.

Links
Github Repo: https://github.com/Shivam010/cloudflare-double-slashes-issue
Hosted on: https://double-slashes-issue.pages.dev

/secure/one

/secure/one

route – https://double-slashes-issue.pages.dev/secure/one

//secure/one

//secure/one

route – https://double-slashes-issue.pages.dev//secure/one

/secure/one?allow

/secure/one?allow

/secure/one?allow

/secure/one?allow route – https://double-slashes-issue.pages.dev/secure/one?allow (that's actually allowed by middleware)

GitHub

GitHub - Shivam010/cloudflare-double-slashes-issue

Contribute to Shivam010/cloudflare-double-slashes-issue development by creating an account on GitHub.

S

Soham•8/12/23, 12:45 PM

Anyway I can make a blog using pages functions and workers for my pages website?

MMy Account I have created a nice web app for exploring purposes I dont know backend stuff ...

D

Dahoom•8/13/23, 11:50 AM

Look in the dashboard, in your pages project in the settings tab there is an environment variable option that you can set and encrypt for both preview and production branches

C

Cretezy•8/13/23, 9:37 PM

Currently trying to test Functions locally using

npx wrangler pages dev .

npx wrangler pages dev .

(

contains a directory with

functions

functions

) and getting the following error:

CCretezy Currently trying to test Functions locally using `npx wrangler pages dev .` (`.`...

J

James•8/13/23, 9:40 PM

Try downgrading to wrangler 3.4.0. 3.5.0 has an issue that's hiding some useful error logs from workerd.

C

Cretezy•8/13/23, 9:41 PM

workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use --test_env=LLVM_SYMBOLIZER=<path>.

workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use --test_env=LLVM_SYMBOLIZER=<path>.

workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use --test_env=LLVM_SYMBOLIZER=<path>.

workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use --test_env=LLVM_SYMBOLIZER=<path>.

C

Cretezy•8/13/23, 9:42 PM

I have LLVM 15.0.7 installed, and

llvm-symbolizer

llvm-symbolizer

is in

$PATH

$PATH

.

J

James•8/13/23, 9:44 PM

any other errors? What's your functions look like?

C

Cretezy•8/13/23, 9:45 PM

LLVM_SYMBOLIZER=(which llvm-symbolizer) npx wrangler@3.4 pages dev .

LLVM_SYMBOLIZER=(which llvm-symbolizer) npx wrangler@3.4 pages dev .

seems to work!

J

James•8/13/23, 9:45 PM

Is there another line perhaps under that one? Can you screenshot again?

J

James•8/13/23, 9:45 PM

...that really should not be required

C

Cretezy•8/13/23, 9:46 PM

J

James•8/13/23, 9:46 PM

ahh okay,

address already in use

address already in use

J

James•8/13/23, 9:46 PM

you have another

workerd

workerd

process open somewhere

C

Cretezy•8/13/23, 9:46 PM

Sorry, there's also another error in there. Port wasn't used before

C

Cretezy•8/13/23, 9:47 PM

Worked once I

kill

kill

ed it

J

James•8/13/23, 9:47 PM

not sure how that happened, but yeah, kill other workerd processes and you should be good

C

Cretezy•8/13/23, 9:47 PM

Yeah works without the env var now too, not sure what happened

C

Cretezy•8/13/23, 9:48 PM

How does functions work locally though? Do I run in the directory that contains

functions

functions

, or in

functions

functions

itself?

C

Cretezy•8/13/23, 9:49 PM

Sorry it actually is working in the parent directory... long day

J

James•8/13/23, 9:49 PM

public
   - index.html
functions
   - some-page.ts

public
   - index.html
functions
   - some-page.ts

J

James•8/13/23, 9:49 PM

yeah, something like that. Glad you got it working

C

Cretezy•8/13/23, 9:49 PM

Thanks

C

Cretezy•8/14/23, 12:53 AM

Hi! I'm having another issue with Cloudflare Pages Function. I am trying to implement Steam login, which is OpenID. Basically Steam redirects to the Worker with some query parameters, and I need to call the Steam API with some of those.

I tested this locally using wrangler, and it worked as expected. I then deployed it, and started getting

403 Forbidden

403 Forbidden

from the Steam API (

https://steamcommunity.com/openid/login

https://steamcommunity.com/openid/login

)

I thought this could have been that Cloudflare IPs are being blocked, so I setup a proxy (and tested it), and it's still doing the same, indicating that it's something else from the Worker runtime that's affecting the request.

For reference, this is the request I am making:

  const body = {
    "openid.assoc_handle": searchParams.get("openid.assoc_handle") ?? "",
    "openid.signed": searchParams.get("openid.signed") ?? "",
    "openid.sig": searchParams.get("openid.sig") ?? "",
    "openid.ns": OPENID.ns,
    "openid.mode": "check_authentication",
    "openid.op_endpoint": OPENID.endpoint,
    "openid.claimed_id": searchParams.get("openid.claimed_id") ?? "",
    "openid.identity": searchParams.get("openid.identity") ?? "",
    "openid.return_to": returnTo,
    "openid.response_nonce": searchParams.get("openid.response_nonce") ?? "",
  };
  const openidResponse = await fetch(
    "https://<steam-proxy>/steamcommunity.com/openid/login",
    {
      method: "POST",
      headers: {
        "Content-Type": "application/x-www-form-urlencoded",
      },
      body: new URLSearchParams(body),
    },
  );

  const body = {
    "openid.assoc_handle": searchParams.get("openid.assoc_handle") ?? "",
    "openid.signed": searchParams.get("openid.signed") ?? "",
    "openid.sig": searchParams.get("openid.sig") ?? "",
    "openid.ns": OPENID.ns,
    "openid.mode": "check_authentication",
    "openid.op_endpoint": OPENID.endpoint,
    "openid.claimed_id": searchParams.get("openid.claimed_id") ?? "",
    "openid.identity": searchParams.get("openid.identity") ?? "",
    "openid.return_to": returnTo,
    "openid.response_nonce": searchParams.get("openid.response_nonce") ?? "",
  };
  const openidResponse = await fetch(
    "https://<steam-proxy>/steamcommunity.com/openid/login",
    {
      method: "POST",
      headers: {
        "Content-Type": "application/x-www-form-urlencoded",
      },
      body: new URLSearchParams(body),
    },
  );

  const body = {
    "openid.assoc_handle": searchParams.get("openid.assoc_handle") ?? "",
    "openid.signed": searchParams.get("openid.signed") ?? "",
    "openid.sig": searchParams.get("openid.sig") ?? "",
    "openid.ns": OPENID.ns,
    "openid.mode": "check_authentication",
    "openid.op_endpoint": OPENID.endpoint,
    "openid.claimed_id": searchParams.get("openid.claimed_id") ?? "",
    "openid.identity": searchParams.get("openid.identity") ?? "",
    "openid.return_to": returnTo,
    "openid.response_nonce": searchParams.get("openid.response_nonce") ?? "",
  };
  const openidResponse = await fetch(
    "https://<steam-proxy>/steamcommunity.com/openid/login",
    {
      method: "POST",
      headers: {
        "Content-Type": "application/x-www-form-urlencoded",
      },
      body: new URLSearchParams(body),
    },
  );

  const body = {
    "openid.assoc_handle": searchParams.get("openid.assoc_handle") ?? "",
    "openid.signed": searchParams.get("openid.signed") ?? "",
    "openid.sig": searchParams.get("openid.sig") ?? "",
    "openid.ns": OPENID.ns,
    "openid.mode": "check_authentication",
    "openid.op_endpoint": OPENID.endpoint,
    "openid.claimed_id": searchParams.get("openid.claimed_id") ?? "",
    "openid.identity": searchParams.get("openid.identity") ?? "",
    "openid.return_to": returnTo,
    "openid.response_nonce": searchParams.get("openid.response_nonce") ?? "",
  };
  const openidResponse = await fetch(
    "https://<steam-proxy>/steamcommunity.com/openid/login",
    {
      method: "POST",
      headers: {
        "Content-Type": "application/x-www-form-urlencoded",
      },
      body: new URLSearchParams(body),
    },
  );

It works locally with

wranger pages dev

wranger pages dev

, but not when deployed. Here's the same in Insomnia (Postman)

C

Cretezy•8/14/23, 12:54 AM

<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n

<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n

<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n

<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n

is what's being returned when deployed

K

kian•8/14/23, 12:55 AM

I'm pretty sure Steam block Cloudflare Workers, and by extension Functions.

K

kian•8/14/23, 12:55 AM

Are you stripping the CF-Worker request header in your proxy?

Hey functions team, I'm trying to deploy a simple hello world function. I am using nuxt.js and juxt

Similar Threads