https://developers.cloudflare.com/workers/platform/tail-workers/ if you're on a paid plan

N

Neiki•5/24/23, 8:26 PM

thanks and yes

NNeiki thanks and yes

N

Neiki•5/24/23, 8:48 PM

nvm sorry i found it, sorry for ping

Original message was deleted

D

dave•5/24/23, 9:11 PM

Correct. It's a bit annoying to have to have different preloading implementations for Chrome vs Safari though. For ease of use, we just stick with doing preloading client side for now.

Kkian Safari is the one I'll be hoping for - Safari on iOS is a big chunk of our users

D

dave•5/24/23, 9:12 PM

and those are the ones with the slow interwebz who you care about usually

D

dave•5/24/23, 9:17 PM

@sathoro btw Supabase staff will turn off rate limiting for your project if you ask them and say it's because you're using a Worker. Don't think you were running into issues yet, but figured I should share the info.

N

Nick Harris•5/24/23, 9:55 PM

Is it possible to use an HTTP proxy server when making outbound fetch calls from a Worker? I have some external services that are IP-restricted, and since CF Worker IPs aren't static I need to proxy it through another server (via tunneling) to make the call.

N

Nick Harris•5/24/23, 10:03 PM

Ah, gotcha, so you just made requests directly to the nginx reverse proxy?

N

Nick Harris•5/24/23, 10:04 PM

Thanks, seems like that'll end up being the lightest solution

W

Walshy•5/24/23, 10:29 PM

looks like you're using JavaScript not TypeScript

W

Walshy•5/24/23, 10:29 PM

if you remove the typing, it should work

W

Walshy•5/24/23, 10:42 PM

what's your full code?

C

Chaika•5/24/23, 10:54 PM

iirc you're missing node_compat? Or browser isn't set? I got that same error when I was setting this up yesterday, and it was fixed by me copying their wrangler.toml, can't remember if it was node_compat specifically or something else though. If you don't have it set at all though, you should

C

Chaika•5/24/23, 10:55 PM

your wrangler.toml should be like:

name = "browser-worker"
main = "src/index.ts"
compatibility_date = "2023-03-14"
node_compat = true
workers_dev = true

browser = { binding = "MYBROWSER", type = "browser" }

name = "browser-worker"
main = "src/index.ts"
compatibility_date = "2023-03-14"
node_compat = true
workers_dev = true

browser = { binding = "MYBROWSER", type = "browser" }

name = "browser-worker"
main = "src/index.ts"
compatibility_date = "2023-03-14"
node_compat = true
workers_dev = true

browser = { binding = "MYBROWSER", type = "browser" }

name = "browser-worker"
main = "src/index.ts"
compatibility_date = "2023-03-14"
node_compat = true
workers_dev = true

browser = { binding = "MYBROWSER", type = "browser" }

Make sure you're not trying to test locally as well. If you're on the latest wrangler/wrangler@3, use

npx wrangler dev --remote

npx wrangler dev --remote

npx wrangler dev --remote

npx wrangler dev --remote

W

Walshy•5/24/23, 11:09 PM

yeah seems like MYBROWSER isn't defined as a browser binding

W

Walshy•5/24/23, 11:26 PM

aww man... you do need 3.0

W

Walshy•5/24/23, 11:27 PM

you can use unsafe for now

[[unsafe.bindings]]
binding = "MYBROWSER"
type = "browser"

[[unsafe.bindings]]
binding = "MYBROWSER"
type = "browser"

[[unsafe.bindings]]
binding = "MYBROWSER"
type = "browser"

[[unsafe.bindings]]
binding = "MYBROWSER"
type = "browser"

N

Neiki•5/25/23, 7:20 AM

i also have an error with tail workers: workers-and-pages-helpTail worker is not working

Kkian https://developers.cloudflare.com/workers/platform/tail-workers/ if you're on a ...

N

Neiki•5/25/23, 7:32 AM

its not working Tail worker is not working

D

divby0•5/25/23, 1:22 PM

when an error happens, the log has an empty

logs

logs

logs

logs and an empty

exceptions

exceptions

exceptions

exceptions field. Weirdly the

outcome

outcome

outcome

outcome field is "ok" even thought the

event.response.status

event.response.status

event.response.status

event.response.status is 500 and clearly not okay. What may have gone wrong? How does the outcome field get set to ok?

K

kianOP•5/25/23, 1:24 PM

If a 500 response is returned by a script then that’s going to be an ok outcome

K

kianOP•5/25/23, 1:24 PM

It’d only be an exception if an unhandled exception occurred

Kkian It’d only be an exception if an unhandled exception occurred

D

divby0•5/25/23, 1:38 PM

Ohhh okay that makes sense. Thank you very much Kian!

K

kianOP•5/25/23, 1:39 PM

export default <ExportedHandler> {
  fetch() {
    return new Response(null, {
      status: 500,
    });
  },
};

export default <ExportedHandler> {
  fetch() {
    return new Response(null, {
      status: 500,
    });
  },
};

export default <ExportedHandler> {
  fetch() {
    return new Response(null, {
      status: 500,
    });
  },
};

export default <ExportedHandler> {
  fetch() {
    return new Response(null, {
      status: 500,
    });
  },
};

That'd cause what you're seeing - where the script outcome was

ok

ok

ok

ok as it didn't encounter any issues but the response status is 500.

https://developers.cloudflare.com/workers/platform/tail-workers/ if you're on a paid plan

Similar Threads

Similar Threads

Similar Threads