Rob Wu

CORS Anywhere does not cache any data. The client (your browser) or destination server may have caching mechanisms, but that's outside the scope of responsibilities of CORS Anywhere. If you...

There is not enough information in this bug report to tell whether the issue is due to your other API endpoint or CORS Anywhere. If you consistently experience the failure...

CORS Anywhere does not treat POST any differently from GET.

Have you seen the documentation of the `fetch` API on MDN? https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/fetch

Since I get mailed fairly often about this, here is a way to use CORS Anywhere in a virtual directory in Nginx. Change directory (e.g. "/cors/") , IP (e.g. 127.0.0.1)...

CORS Anywhere is a Node.js application. A FTP server just serves files. You need to upload the CORS Anywhere application to a server (=hardware/runtime environment) that launches the CORS Anywhere...

This is not part of the current functionality, but I can add it. Restricting to "file types" is pointless, because it can easily be bypassed. For example, if you want...

> Regarding the PDF, I can't agree with you there - after all, anything you add to the URL will be in the __query string__ and not the __path__ (`urlObject.pathname`),...

I'd keep this issue open. For the public demo, I am currently applying a patch on top of the default source that hard-codes checks to enforce blacklists for the few...

There is no built-in logging functionality. If you want to log all outgoing requests, including redirects, fork the library and add logging here: https://github.com/Rob--W/cors-anywhere/blob/4814647a9d21f14858da282387a4295c17f2851d/lib/cors-anywhere.js#L133