On 8/5/24 10:30, Odhiambo Washington via Mailman-users wrote:
Actually, what I mean is that CF is proxying requests to the host named m3-lists.kictanet.or.ke. I do not have any configuration other than DNS proxying at CF.
dig a mm3-lists.kictanet.or.ke
...
mm3-lists.kictanet.or.ke. 300 IN A 172.67.167.73
mm3-lists.kictanet.or.ke. 300 IN A 104.21.11.217
Both of those are cloudflare IPs, and why 2?
So when you talk to m3-lists.kictanet.or.ke via a browser, it's CF IP who you talk to and it in turn talks to the host directly.
And how is that configured?
So the IP address you see in the logs is CF's IP address, not yours, not mine and CF are doing some caching. That's why they are requesting for expired files.
Why is cloudfare trying to access /opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css locally if all it is doing is proxying the request to the actual mailman server?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan