add workaround to URL parser for Cloudflare Reverse Proxy bug #388
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.