cloudflare-cors-anywhere VS add-cors

Yes, unfortunately if the "foreign" sources don't support CORS, you'd have to use a CORS proxy... If you want to self-host, there's one at https://github.com/Zibri/cloudflare-cors-anywhere that can be deployed to CloudFlare Workers (the code is a bit messy though).

GitHub supports CORS for raw data for example, that's why I put it in the sample queries.

here’s the one I use

You could probably add cloudflare workers as an option. There's an example CORS friendly proxy here: https://github.com/Zibri/cloudflare-cors-anywhere

Guessing normal use would fit in their free plan.

You should be able to do this with a third party service such as https://fixtur.es/en/team/philadelphia-union

I route my remote calendars through Cloudflare workers for a modicum of privacy from random third party services. It's as simple as running a basic open source relay: https://github.com/Zibri/cloudflare-cors-anywhere

Otherwise, if it is on a server, when you make the request, add a header like “Origin”: “https://(sitename).com/“ where sitename would be the URL (not yours, in this case Pipedream’s) to avoid CORS. If worse comes to worse though, you could make your own proxy using Cloudflare Workers. There’s also Cloudflare CORS-Anywhere and CORSFlare

Wait I found this repo for doing what I want, I’ll see if it works

git clone https://github.com/das-jishu/add-cors.git cd add-cors/ npm install heroku create cors-everywhere //cors-everywhere is an example. Use a unique name for heroku to create. git push heroku master