Cloudflare

anyone any ideas above on whats wrong with how im setting my secrets?

we do several minute long requests it works fine actually

the client just needs to stay connected lol

i have an api endpoint api/v1/hello on a different server,  and i am using worker as a proxy server, but i am not able to pass the required headers to the sub request in the worker fetch request

from client side, when i pass the headers its working but its not being forwarded to the request server

```app.get("*", async (ctx) => {
  const cacheurl = new URL(ctx.req.url);
  // console.log(cacheurl);
  console.log(ctx.req.headers.get("pix-api"));
  let headers = new Headers();
  headers.set("pix-api", "api-key");
  cacheurl.host = "example.com";
  const result = await fetch(cacheurl, {
    headers,
  });

  // response = new Response(result.body);
  // ctx.executionCtx.waitUntil(cache.put(cacheKey, response.clone()));
  return new Response(result.body, {
    headers: {
      ...headers,
      "res-pix-api": result.headers.get("pix-api") || "Not Found",
    },
  });```

all of our public facing API services are on Cloudflare Workers, and even most of the private APIs are also on Workers.

`headers` is always going to be blank other than `pix-api` in that scenario.

cloudflare fetch is adding bom to the data, how can i stop this?

You're not using the request headers, you define `headers` with `let headers = new Headers();` which is an empty object and then only contains the `pix-api` header which you set.

If you want to use the request headers, that'd be `ctx.req.headers`

looks like this headers is also not getting there

hi 😄 
with the upcoming workers snippets, in theory i should be able to make a "free" load balancer for an api; and the only real limit should be the dns resolution fees, is that correct (which only start at 1m/month)?

Snippets can only make 1 subrequest so you wouldn't be able to do that.

Well, you can do Math.random and select a subdomain based on that

but you wouldn't be able to hit one and then decide to fallback if it failed

can i somehow send me an email or sending with an webhook if that happens again? like let me notify
https://cdn.discordapp.com/attachments/779390076219686943/1110971634870923367/image.png

is there a place where we can see how much deployments we already made?

i cant find anything to workers or crons in the notifications tab, only about pages

yeah, fallback would not be a possibility. but i could do either random, or based on some "hash"  of the request ip + maybe some user cookie or sth.

Hi, given that workers are now able to connect to an arbitrary TCP port, is regular fetch from non-http ports (like 8080) now allowed?

<@883084594218430464> then, if 1 request can be split to multiple subdomains, one could assign only functioning servers to those subdomains, i.e. if i know one of my servers is down, i change its subdomain to point to a known good server