I'm not sure about packages, but you might be interested in the new rate limiter bindings announced

W

Walshy•4/7/24, 8:57 PM

the type is based on the extension of the path

W

Walshy•4/7/24, 8:57 PM

Since it's at request time that it's categorised

W

Walshy•4/7/24, 9:01 PM

The network tab shows requests and their responses, the category it puts it in is based on the request path (e.g.

is marked as a document,

/abc.js

/abc.js

/abc.js

/abc.js is marked as js)

Things don't show up after a response, it's on request so there's no content-type available to use

S

Silent•4/7/24, 10:47 PM

Does returning response with status code 500 automatically send this page?
I can not tthink of anything else that could do this, the docs say its from a javascript exception but locally it runs fine no exceptions

K

kian•4/7/24, 10:49 PM

Does returning response with status code 500 automatically send this page?

Nope

W

Walshy•4/7/24, 11:32 PM

no there's an exception happening, check the logs - https://developers.cloudflare.com/workers/observability/logging/real-time-logs/

N

naourass•4/8/24, 2:32 AM

In my local wrangler project that is not deployed (yet), is it possible to add a binding to some Worker that is already deployed (so I can make RPC calls from the local project to the deployed worker)?

Original message was deleted

H

Hello, I’m Allie!•4/8/24, 10:22 AM

Responses from Workers, or

fetch

fetch

Responses within a Worker?

PPeter Mbanugo Hi. I use `node_compat = true` for an old workers projects. I see there's `compa...

H

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

They are not.

node_compat

node_compat

node_compat

node_compat involves bundling polyfills into your Worker.

nodejs_compat

nodejs_compat

nodejs_compat

nodejs_compat are native Node-ish modules that you can use without changes to your Worker itself. Wherever possible, we recommend the compat flag, but some packages require

node_compat

node_compat

node_compat

node_compat instead

Original message was deleted

B

bun•4/8/24, 10:26 AM

it should always be set yes. you cant even override that header

Original message was deleted

H

Hello, I’m Allie!•4/8/24, 10:27 AM

Looks like it is set to 0?

H

Hello, I’m Allie!•4/8/24, 10:27 AM

At least at a cursory glance...

B

bun•4/8/24, 10:28 AM

oh you mean requests to workers nvm then

H

Hello, I’m Allie!•4/8/24, 10:29 AM

At least when I use postman, and toggle the

content-length

content-length

content-length

content-length off

B

bun•4/8/24, 2:33 PM

why is duration even measured in GB-s ? isn't it more intuitive to measure in pure seconds and just account for 128mb-s, is it because cloudflare is trying to align with other cloud providers standards or like they are trying to make it confusing ?

W

Walshy•4/8/24, 2:34 PM

Other providers use that and we previously did too (for Unbound), we're moving to Standard so duration isn't even a metric that will be billed on soon enough (for most customers it isn't already)

B

bun•4/8/24, 2:34 PM

wait so standard usage model doesnt bill on duration at all?

W

Walshy•4/8/24, 2:35 PM

nope

W

Walshy•4/8/24, 2:35 PM

standard is requests + cpu time

W

Walshy•4/8/24, 2:35 PM

https://developers.cloudflare.com/workers/platform/pricing/#pricing

B

bun•4/8/24, 2:36 PM

well lets say one worker rpc invokes another worker, is it still considered a request?

B

bun•4/8/24, 2:37 PM

it is a request for DO's but not sure about workers

Bbun well lets say one worker rpc invokes another worker, is it still considered a re...

I

Isaac McFadyen•4/8/24, 2:59 PM

Yes.

A

Arma•4/8/24, 4:26 PM

Does the workers runtime perform JIT optimisations? It says V8 in the documentation but im not sure Turbofan is enabled

P

Piero512•4/8/24, 4:31 PM

Hey, do you know if CF filters Authorization header to workers?

P

Piero512•4/8/24, 4:31 PM

I have a code that used to work but now it's broken

R

R1CH•4/8/24, 4:31 PM

I doubt it, that would break many use cases.

P

Piero512•4/8/24, 4:34 PM

async fetch(request: Request, env, ctx) {
    if (request.method === 'POST') {
      console.log("Request headers: ")
      console.log(JSON.stringify(request.headers));
      if (request.headers['Authorization']) {
        const auth: string = request.headers['Authorization'];
        const authRegex = /Bearer (\w+)/g;
        const match = auth.match(authRegex);
        if (match) {
          // do stuff
        }
      } else {
        return new Request("Unauthorized request", {status:403});
      }
}

async fetch(request: Request, env, ctx) {
    if (request.method === 'POST') {
      console.log("Request headers: ")
      console.log(JSON.stringify(request.headers));
      if (request.headers['Authorization']) {
        const auth: string = request.headers['Authorization'];
        const authRegex = /Bearer (\w+)/g;
        const match = auth.match(authRegex);
        if (match) {
          // do stuff
        }
      } else {
        return new Request("Unauthorized request", {status:403});
      }
}

async fetch(request: Request, env, ctx) {
    if (request.method === 'POST') {
      console.log("Request headers: ")
      console.log(JSON.stringify(request.headers));
      if (request.headers['Authorization']) {
        const auth: string = request.headers['Authorization'];
        const authRegex = /Bearer (\w+)/g;
        const match = auth.match(authRegex);
        if (match) {
          // do stuff
        }
      } else {
        return new Request("Unauthorized request", {status:403});
      }
}

async fetch(request: Request, env, ctx) {
    if (request.method === 'POST') {
      console.log("Request headers: ")
      console.log(JSON.stringify(request.headers));
      if (request.headers['Authorization']) {
        const auth: string = request.headers['Authorization'];
        const authRegex = /Bearer (\w+)/g;
        const match = auth.match(authRegex);
        if (match) {
          // do stuff
        }
      } else {
        return new Request("Unauthorized request", {status:403});
      }
}

P

Piero512•4/8/24, 4:35 PM

Is this a wrong way to read an authorization header?

R

R1CH•4/8/24, 4:39 PM

try

request.headers.get('Authorization')

request.headers.get('Authorization')

request.headers.get('Authorization')

request.headers.get('Authorization')

P

Piero512•4/8/24, 4:41 PM

I don't regularly write JS so I am not sure why is that [] is not equal to that but hopefully it works.

P

Piero512•4/8/24, 4:43 PM

Hmm, I get a different error now

P

Piero512•4/8/24, 4:43 PM

Thanks for the help

R

R1CH•4/8/24, 5:06 PM

Is there a limit to the number of routes that can be configured in wrangler.toml?

R

R1CH•4/8/24, 5:06 PM

Thanks, more than enough for my use case then.

R

R1CH•4/8/24, 5:21 PM

Anyone else seeing 524s from a bunch of worker API endpoints?

C

Chaika•4/8/24, 5:25 PM

no, everything seems ok to me

C

Chaika•4/8/24, 5:25 PM

sometimes the dashboard decides it wants a break for a bit, possible it was only for a second

I'm not sure about packages, but you might be interested in the new rate limiter bindings announced

Similar Threads