Those kind of error pages usually appear if your browser is making a request that isn't valid accord

Those kind of error pages usually appear if your browser is making a request that isn't valid according to the HTTP specification.

Isaac McFadyenOP•11/26/23, 5:06 PM

For example, if you send a body in a GET request then you might get that. Or if you send a header name that isn't valid. Or any number of other things really.

Isaac McFadyenOP•11/26/23, 5:06 PM

Take a look and make sure that the POST request you're making is valid and looks fine syntactically

scotto•11/26/23, 6:07 PM

There is any good project example for workers and D1 to start from ? Like with multiples APIs / files

dave•11/26/23, 7:47 PM

Question, for those of you who have had their Workers DDoS'd, how was the experience? Does CF do a decent job of blocking requests before they hit the Workers?

dave•11/26/23, 7:51 PM

nice. I was debating if I should use Google Cloud Run without Workers, but I think it makes sense to always use Workers in front.

dave•11/26/23, 7:51 PM

it does increased the cost from $0.20/million requests to $0.50/million requests when stacking a Worker on top, but the benefit of DDoS protection makes it nice.

Original message was deleted

zegevlier•11/26/23, 8:04 PM

You can even block by header value on, so if they did have a valid authentication token somehow they would still get blocked.

meow•11/26/23, 9:29 PM

Is middleware only available for Cloudflare Pages and not Workers?

James•11/26/23, 9:41 PM

Middleware is a thing for Functions since they have file-based routing, and the concept of Middleware makes a lot of sense there for handling auth, etc.

James•11/26/23, 9:41 PM

Many popular routers and frameworks for Workers also support Middleware though, such as https://hono.dev/

Fun Miles•11/27/23, 12:12 AM

My cron worker job got killed for exceeding time (32,000 ms). Is there a way to increase that number?

Fun Miles•11/27/23, 12:15 AM

The docs, under CPU time say

When the schedule interval is more than 1 hour, a scheduled Worker may run for up to 15 minutes.

When the schedule interval is more than 1 hour, a scheduled Worker may run for up to 15 minutes.

. My job runs once per month.

Shane•11/27/23, 12:43 AM

wrangler 3.17.1
-------------------
⎔ Starting local server...
✘ [ERROR] service core:user:search: Uncaught TypeError: Incorrect type for map entry 'DEFAULT_PAGE_SIZE': the provided value is not of type 'function or ExportedHandler'.

Is there a way to get a more detailed error here? I removed default_page_size from my code entirely and I'm still getting the error for some reason

Shane•11/27/23, 12:47 AM

odd, no error when I turn off local mode

Shane•11/27/23, 12:52 AM

tried deleting node modules and .wrangler and reinstalling with yarn, no luck there either, something gotta be cached somewhere

Shane•11/27/23, 12:57 AM

ofc it just randomly works now without me changing anything Sadge

IIsaac McFadyen Those kind of error pages usually appear if your browser is making a request tha...

fengyangsi•11/27/23, 2:36 AM

I'm sure the request is valid, and when I

wrangler dev

wrangler dev

in local it work, but

wrangler deploy

wrangler deploy

to cloudflare it doesn't work

Isaac McFadyenOP•11/27/23, 2:37 AM

It's unrelated to Wrangler. That error page is something you'd receive before the request even hits the Worker, nothing you're doing in your Worker should trigger that.

fengyangsi•11/27/23, 2:42 AM

I even not send any body when i test, just a null POST, in local, it return

Can't deserialize json to pass value

Can't deserialize json to pass value

and 400 write in my code, but in cloudflare, it return 403

#[event(fetch)]
async fn main(mut req: Request, _env: Env, _ctx: Context) -> Result<Response> {
    if req.method() == Method::Post{
        if let Ok(body) = req.text().await{
            match serde_json::from_str::<TVSignal>(&body) {
                Ok(tvs)=> {
                    match Fetch::Request(tvs.request()).send().await {
                        Ok(_) => Response::ok("Success"),
                        Err(_) => Response::error("Error to send request to OKX", 502),
                    }
                },
                Err(_) => Response::error("Can't deserialize json to pass value", 400),
            } 
        }else {
            Response::error("Need text body",400)
        }
    }else {
        Response::error("There are apis, please request with POST",400)
    }
}

#[event(fetch)]
async fn main(mut req: Request, _env: Env, _ctx: Context) -> Result<Response> {
    if req.method() == Method::Post{
        if let Ok(body) = req.text().await{
            match serde_json::from_str::<TVSignal>(&body) {
                Ok(tvs)=> {
                    match Fetch::Request(tvs.request()).send().await {
                        Ok(_) => Response::ok("Success"),
                        Err(_) => Response::error("Error to send request to OKX", 502),
                    }
                },
                Err(_) => Response::error("Can't deserialize json to pass value", 400),
            } 
        }else {
            Response::error("Need text body",400)
        }
    }else {
        Response::error("There are apis, please request with POST",400)
    }
}

fengyangsi•11/27/23, 2:45 AM

maybe this is a SSL error? local use http and http1.1 but couldflare use https and http2?

Unsmart•11/27/23, 2:46 AM

Its not an SSL error or an error in the workers code. Cloudflare does some basic validation on requests and if it does not pass the basic validation you get the generic 403 error. That generic 403 error means it never even attempted to forward the request to your worker or to an origin

UUnsmart Its not an SSL error or an error in the workers code. Cloudflare does some basic...

fengyangsi•11/27/23, 2:48 AM

thank, i understand, but why my request can't pass validation?

Unsmart•11/27/23, 2:49 AM

Not sure. What browser are you using, and how are you doing the request?

fengyangsi•11/27/23, 2:56 AM

firefox

Ffengyangsi firefox

Unsmart•11/27/23, 2:58 AM

Yeah that request is getting blocked because of the host header being "127.0.0.1:8787" the host header should be whatever the domain is.

UUnsmart Yeah that request is getting blocked because of the host header being "127.0.0.1...

fengyangsi•11/27/23, 3:06 AM

ok, it work on workers.dev, but in my domain, it return 405

fengyangsi•11/27/23, 3:11 AM

it's because the pages?

fengyangsi•11/27/23, 3:32 AM

just a router error, it can work now, thank you

Cedrick•11/27/23, 6:06 PM

Hello everyone, I am integrating the workerAI with Langchain4j to bring visibility to this great asset https://github.com/clun/langchain4j/tree/provider-workerai. Most of the features are their. I have question regarding the

text-to_Image

text-to_Image

(1) a few times i got the "upstream too busy", (2) is there any plan to add the resolution in the input request (3) what would be great value for num steps... i can try and guess but explanation would help

Pato•11/27/23, 7:12 PM

hey im getting this error with wrangler

✘ [ERROR] Error while creating remote dev session: TypeError: fetch failed
      at fetch
 {
    cause: Error: connect ETIMEDOUT 2606:4700:3031::ac43:cb34:443
        at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
      errno: -60,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '2606:4700:3031::ac43:cb34',
      port: 443
    }
  }

✘ [ERROR] Error while creating remote dev session: TypeError: fetch failed
      at fetch
 {
    cause: Error: connect ETIMEDOUT 2606:4700:3031::ac43:cb34:443
        at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
      errno: -60,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '2606:4700:3031::ac43:cb34',
      port: 443
    }
  }

Pato•11/27/23, 7:12 PM

it worked fine like 5 minutes ago

Pato•11/27/23, 7:26 PM

anyone knows what might be going on? There`s nothing on cloudflares status page

CCedrick Hello everyone, I am integrating the workerAI with Langchain4j to bring visibili...

Cedrick•11/28/23, 1:15 AM

https://github.com/langchain4j/langchain4j/pull/320

GitHub

Support for WorkerAI Provider by clun · Pull Request #320 · langcha...

Support for Worker AI
CloudFlare opened a Beta of a new service Called WorkerAI
https://developers.cloudflare.com/workers-ai/
They do provide a REST API for different operations.

Text Generation
T...

gonz•11/28/23, 10:53 AM

Hi all. Say I have a zone called

foo.bar.com

foo.bar.com

and a workers route for

*.foo.bar.com/*

*.foo.bar.com/*

that goes to my worker, plus a proxied DNS record for

*.foo.bar.com

*.foo.bar.com

. All that works fine. Then we decide to create a zone for

bar.com

bar.com

and migrate off

foo.bar.com

foo.bar.com

into this zone. Added the same proxied DNS record to this

bar.com

bar.com

zone and the same workers route. Issue we're seeing is that the requests seem to go straight to the origin server but they don't seem to be hitting the worker at all.

Any ideas/thoughts?

Correction: it seems to break whenever I remove the workers route from the old

foo.bar.com

foo.bar.com

zone. I want the new

bar.com

bar.com

to process these requests, not the old zone

Fun Miles•11/28/23, 1:44 PM

What is the CPU limit accounting when using a bound worker with the new billing system? Does the worker called with fetch get counted as part of the caller's CPU usage, or does it get its own limit?

Fun Miles•11/28/23, 1:46 PM

If it were called via the network, it would get its own limit and the caller time would pause while awaiting for the result of the fetch, right? Is it similar for a bound worker call?

liam | helius.dev•11/28/23, 8:34 PM

Are there any plans to reduce the cold start latency of workers? Its quite bad right now

Original message was deleted

liam | helius.dev•11/28/23, 8:43 PM

Do you have any idea how much this can help/what target cold start time is? Articles like this even claim there is zero cold start, but in practice I see anywhere between 50-500ms

liam | helius.dev•11/28/23, 8:50 PM

Spot checking response times from different locations, comparing first to subsequent requests. I had a lengthy convo with a support engineer a while ago but he wasn't able to figure out why with worker was impacted in this way, but without wasn't, so I just assume its something weird in the worker runtime

Lliam | helius.dev Do you have any idea how much this can help/what target cold start time is? Arti...

Hello, I’m Allie!•11/28/23, 8:56 PM

Basically, below 1 MiB you use Quicksilver, the DB that supports Zero Cold Starts. Above 1 MiB, you run from Cold Storage, which does not

HHello, I’m Allie!Basically, below 1 MiB you use Quicksilver, the DB that supports Zero Cold Start...

liam | helius.dev•11/28/23, 8:57 PM

Got it, do you have any sense of the latency distribution for running off of quicksilver vs cold storage?

Lliam | helius.dev Got it, do you have any sense of the latency distribution for running off of qui...

Hello, I’m Allie!•11/28/23, 8:58 PM

It should just be an instant drop off, like you are observing

Hello, I’m Allie!•11/28/23, 8:58 PM

If you get it below the limit, then it should just be 0(minus TLS start/other stuff)

HHello, I’m Allie!It should just be an instant drop off, like you are observing

liam | helius.dev•11/28/23, 9:00 PM

When I deploy this is what I see, is the limit based on compressed or uncompressed? Seems its already under but maybe something is still sending it to cold storage since its close?

Total Upload: 957.07 KiB / gzip: 182.93 KiB

Total Upload: 957.07 KiB / gzip: 182.93 KiB

Lliam | helius.dev When I deploy this is what I see, is the limit based on compressed or uncompress...

Hello, I’m Allie!•11/28/23, 9:00 PM

Compressed. Just to be sure, are you paying for Workers atm?

HHello, I’m Allie!Compressed. Just to be sure, are you paying for Workers atm?

liam | helius.dev•11/28/23, 9:01 PM

yeah, enterprise and unbound

Lliam | helius.dev yeah, enterprise and unbound

Hello, I’m Allie!•11/28/23, 9:06 PM

Weird…

Hello, I’m Allie!•11/28/23, 9:06 PM

Yeah, not sure what else could be causing that

Chaika•11/28/23, 9:10 PM

The other thing is about how your worker runs. If you use a route that specifies a specific path the magical cold start stuff can't work

Chaika•11/28/23, 9:10 PM

https://blog.cloudflare.com/eliminating-cold-starts-with-cloudflare-workers/

For now, this is only available for Workers that are deployed to a “root” hostname like “example.com” and not specific paths like “example.com/path/to/something.” We plan to introduce more optimizations in the future that can preload specific paths.

Edit: If it's more then ~50ms then it sounds more like global scope then cold start not working though, tcp connect isn't that long

#[event(fetch)] async fn main(mut req: Request, _env: Env, _ctx: Context) -> Result<Response> { if req.method() == Method::Post{ if let Ok(body) = req.text().await{ match serde_json::from_str::<TVSignal>(&body) { Ok(tvs)=> { match Fetch::Request(tvs.request()).send().await { Ok(_) => Response::ok("Success"), Err(_) => Response::error("Error to send request to OKX", 502), } }, Err(_) => Response::error("Can't deserialize json to pass value", 400), } }else { Response::error("Need text body",400) } }else { Response::error("There are apis, please request with POST",400) } }

✘ [ERROR] Error while creating remote dev session: TypeError: fetch failed at fetch { cause: Error: connect ETIMEDOUT 2606:4700:3031::ac43:cb34:443 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) { errno: -60, code: 'ETIMEDOUT', syscall: 'connect', address: '2606:4700:3031::ac43:cb34', port: 443 } }

Those kind of error pages usually appear if your browser is making a request that isn't valid accord

Similar Threads

Similar Threads

Similar Threads