example.com/cdn-cgi/trace on your tunnel hostname) and in your tunnel logs, that your tunnel is connecting to a nearby location as well, not too related to Workers thoughctx.waitUntil() can have a longer execution time too. Its been 30s of wall-clock duration, and I could really use an increase time limit there.@vercel/og inside a worker. But @cloudflare/pages-plugin-vercel-og uses an older version. BLOCK cf.worker.upstream_zone != "my.domain"example.com/cdn-cgi/tracectx.waitUntil()Simultaneous open connections
You can open up to six connections simultaneously, for each invocation of your Worker. The connections opened by the following API calls all count toward this limit:
- the fetch() method of the Fetch API.const results = await Promise.all([
fetch(url1),
fetch(url2),
fetch(url3),
fetch(url4),
fetch(url5),
fetch(url6),
fetch(url7), // Exceeds the limit of 6
]);@vercel/og@cloudflare/pages-plugin-vercel-ogconst start = performance.now()
await fetch('https://unweb.io/healthcheck').then(x => x.text())
return new Response(String(performance.now() - start));export default {
async fetch(req, env): Promise<Response>
{
// https://developers.cloudflare.com/workers/runtime-apis/bindings/rate-limit/
const ipAddress = req.headers.get("cf-connecting-ip") || "";
const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress })
if (!success)
return new Response(`429 Failure – rate limit exceeded for ${ipAddress}`, { status: 429 });