Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Geo-targeted content #4694

Open
kof opened this issue Jan 1, 2025 · 1 comment
Open

Geo-targeted content #4694

kof opened this issue Jan 1, 2025 · 1 comment
Labels
complexity:medium Up to 1 week of work prio:2 Always look for prio:1 issues first before working on prio:2 type:feat Features and enhancements

Comments

@kof
Copy link
Member

kof commented Jan 1, 2025

As a designer I want to be able to provide geolocation data to the Resource API endpoint so that the backend can deliver different content depending on the visitor's origin.

Proposed solution is to expose cloudflare's IP geolocation data as part of system variable. Then take that and pass it to the API endpoint

https://developers.cloudflare.com/network/ip-geolocation/
@kof kof added type:feat Features and enhancements complexity:medium Up to 1 week of work prio:2 Always look for prio:1 issues first before working on prio:2 labels Jan 1, 2025
@kof
Copy link
Member Author

kof commented Jan 1, 2025 •
edited
Loading

Negative implication: edge cache would be probably empty most of the time when geodata is being used, so the API origin is better be fast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
complexity:medium Up to 1 week of work prio:2 Always look for prio:1 issues first before working on prio:2 type:feat Features and enhancements
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kof