Known issues

Below are some known bugs and issues to be aware of when using Cloudflare Workers.

​​ Route specificity

• When defining route specificity, a trailing /* in your pattern may not act as expected.

Consider two different Workers, each deployed to the same zone. Worker A is assigned the example.com/images/* route and Worker B is given the example.com/images* route pattern. With these in place, here are how the following URLs will be resolved:

// (A) example.com/images/*
// (B) example.com/images*

"example.com/images"
// -> B
"example.com/images123"
// -> B
"example.com/images/hello"
// -> B

You will notice that all examples trigger Worker B. This includes the final example, which exemplifies the unexpected behavior.

When adding a wildcard on a subdomain, here are how the following URLs will be resolved:

// (A) *.example.com/a 
// (B) a.example.com/* 

"a.example.com/a"
// -> B

​​ wrangler dev

• When running wrangler dev, all outgoing requests are given the cf-workers-preview-token header, which Cloudflare recognizes as a preview request. This applies to the entire Cloudflare network, so making HTTP requests to other Cloudflare zones is currently discarded for security reasons. To enable a workaround, insert the following code into your Worker script:

const request = new Request(url, incomingRequest);
request.headers.delete('cf-workers-preview-token');
return await fetch(request);

​​ Custom ports

For Workers subrequests, custom ports are ignored when using HTTPS and are instead always sent to port 443. When using HTTP, custom ports are respected.

For example:

await fetch('https://example.com:1234/foo')

is the equivalent of:

await fetch('https://example.com/foo')