CloudFlare worker for ICS public calendars from Google
Go to file
Emil Lerch 052835beda
support for google 'secret address'
2020-04-14 14:09:10 -07:00
.eslintrc.js initial commit, deployed on googleics.lerch.org 2020-04-14 11:35:25 -07:00
.gitignore initial commit, deployed on googleics.lerch.org 2020-04-14 11:35:25 -07:00
.prettierrc initial commit, deployed on googleics.lerch.org 2020-04-14 11:35:25 -07:00
LICENSE initial commit, deployed on googleics.lerch.org 2020-04-14 11:35:25 -07:00
README.md initial commit, deployed on googleics.lerch.org 2020-04-14 11:35:25 -07:00
index.js support for google 'secret address' 2020-04-14 14:09:10 -07:00
package-lock.json initial commit, deployed on googleics.lerch.org 2020-04-14 11:35:25 -07:00
package.json initial commit, deployed on googleics.lerch.org 2020-04-14 11:35:25 -07:00
wrangler.toml initial commit, deployed on googleics.lerch.org 2020-04-14 11:35:25 -07:00

README.md

GoogleICS

Allows for a proxy from CloudFlare to public calendars on google in iCS format.

This will allow for requests to Google from a mobile device to not come from a geolocatable IP address. Using CloudFlare workers for this also gets you to use a cached edge location. Technically Google tracking would still be available at a regional level (constrained to CloudFlare's edge locations). However, Google would lose the ability to track to a single user.

Specifically, they will get:

  • Time and IP address of CloudFlare edge location
  • The following custom header: CDN-Loop: cloudflare

Note that CloudFlare has full knowledge of requests, etc, so this is somewhat trading of trust from Google (AdTech company) for CloudFlare (makes money from CDN and DDOS mitigation).