https://www.cloudflare.com/trust-hub/reporting-abuse/
Learn how to report abuse to Cloudflare, how to categorize the abuse you report, what information to include in your report, how to report anonymously, and more.

Route pattern matching considers the entire request URL, including the query parameter string. Since route patterns may not contain query parameters, the only way to have a route pattern match URLs with query parameters is to terminate it with a wildcard, *.Is there a way to change this behavior to ignore the query string?
example.com/path and another example.com/path?*wrangler config then there is no way for it to be accessedworkers_dev = false when using a wrangler.tomlno-store request header in my Worker subrequests?



ctx.waitUntil() with a promise that manually resolves when the stream closes, and now I can do cleanup within that promise, but now I have no way to know that the client has disconnected and ctx.waitUntil() will just be aborted by the runtime 30s or so after the client disconnects.: comment) to test if the client is alive so that I can cleanup before that 30s elapses... is that correct? Any way to know immediately when a client has disconnected?await stream.write(...) rejects immediately if the client is disconnected, however if subclassing a ReadableStream, then controller.enqueue(...) does not throw and neither is underlyingSource.cancel() called when the client disconnects?wrangler pages deploy --branch=pr123 and it will automatically wire the preview environment with URL pr123.mypage.pages.dev. I'm struggling to do the same with a worker, because the environment and routes have to be specified in wrangler.toml. I'd be fine with deploying to the same preview env (for the variables), but then I'd need the route with the slug (pr123) to be updated to always point to the correct deployment ID. There will be multiple PRs active at the same time. Thanks!


ReadableStreamBYOBReader.readAtLeast(minBytes, bufferArrayBufferView) as perReturns a promise with the next available chunk of data read into a passed-in buffer. The promise will not resolve until at least minBytes have been read.
minBytes available? A little bit of sanity would say that it would resolve with the buffer partially filled with the available bytes, rather than rejecting, but that contradicts the absolute statement "The promise will not resolve until at least minBytes have been read". Can someone confirm and perhaps update the docs?
example.com/pathexample.com/path?*workers_dev = falseno-storectx.waitUntil()ctx.waitUntil(): commentawait stream.write(...)ReadableStreamcontroller.enqueue(...)underlyingSource.cancel()wrangler pages deploy --branch=pr123pr123.mypage.pages.devpr123ReadableStreamBYOBReader.readAtLeast(minBytes, bufferArrayBufferView)minBytes Inbound requests to your Worker. Cloudflare does not bill for subrequests you make from your Worker.