Can we ignore CF-Headers via configuration? #4455
-
|
hello, I'm facing the same issue like #2767 But cloudflare doesn't allow to remove CF-* headers via the rules anymore. My setup is the following: because of proxing, CF-Connected-IP header are IP of the vercel servers, but X-Forwarded-For are the user IP adress. Since plausible prefer to use CF header, geolocation is completely wrong... can we somehow ignore the Headers, without removing them via putting another reverse-proxy like nginx to strip them? since CF Tunnels are already a reverse proxy itself, and reverse proxy to reverse proxy are probably not a great idea... |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I'm sorry, I re-read the documentations about rules, and seems like I tried to overwrite the cf-connecting-ip header instead of removing it ... so now everything is working as intented. |
Beta Was this translation helpful? Give feedback.
I'm sorry, I re-read the documentations about rules, and seems like I tried to overwrite the cf-connecting-ip header instead of removing it ... so now everything is working as intented.