Read commit comments. A Cors-anywhere instance behind Cloudflare's WAF/reverse proxy, is unusable because of the "//" to "/" bug that is all over CF's technology. Why someone would use cors-anywhere on node on aws, instead of writing a Cloudflare Worker to do the same thing, when they are a cloudflare customer, is a different story. Without this patch, cors-anywhere sometimes bizarrely shows the "showUsage" page when behind Cloudflare, but works perfect connecting to AWS or localhost directly from chrome. Even if this patch isn't accepted, its a warning that CA has major problems behind CFs WAF.
Read commit comments. A Cors-anywhere instance behind Cloudflare's WAF/reverse proxy, is unusable because of the "//" to "/" bug that is all over CF's technology. Why someone would use cors-anywhere on node on aws, instead of writing a Cloudflare Worker to do the same thing, when they are a cloudflare customer, is a different story. Without this patch, cors-anywhere sometimes bizarrely shows the "showUsage" page when behind Cloudflare, but works perfect connecting to AWS or localhost directly from chrome. Even if this patch isn't accepted, its a warning that CA has major problems behind CFs WAF.