How will this work with geography based used cases (e.g. Geo-filtering / Geo-access)?

buettner / private-prefetch-proxy

Proposal to use a CONNECT proxy to obfuscate the user IP address for privacy-enhanced prefetching.

32 stars 6 forks source link

How will this work with geography based used cases (e.g. Geo-filtering / Geo-access)? #1

Closed KenjiBaheux closed 3 years ago

KenjiBaheux commented 3 years ago

IP address can be used for geography based features such as filtering or restricting access to region locked content, etc.

On prefetches handled by a privacy prefetch proxy, the IP visible by CDN/websites will be the proxy's IP address, not the user's IP address.

KenjiBaheux commented 3 years ago

For regional locks and other features that depends on a location derived from the user's IP address, the following options come to mind:

Perform a check at navigation time (e.g. a sub-resource or JS request which will have the user's IP address).
Using a private prefetch proxy that's located in the same geo (country level) as the user.
Reject the prefetching requests (Purpose: prefetch HTTP header) for content that's known to be subject to geo conditions.

jeremyroman commented 3 years ago

I guess the fourth option would be for the client or proxy to resolve the geography to some large granularity (e.g. country) and send that information somewhere.