Imbolc

The meaning of 0.x version is exactly the opposite :) > Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT...

The IP is certainly parsed from headers, so your approach is correct. But the provided example is too complex, as usual try to maximally simplify it to locate the bug.

Hi :) Make sure you read the [why different extractors](https://docs.rs/axum-client-ip/latest/axum_client_ip/#why-different-extractors) section and understand the security implications of this approach. I believe in your situation it's better to use `SecureClientIp` instead...

> CF Header, and if that doesn't exist, try XRealIP, and if that doesn't exist, take the ConnectInfo IP Let's say you aren't behind CF, then someone could just add...

I don't understand, aren't your trying to get a user ip? If so, how ip ranges of CF could help?

I'm not sure what you mean by "IPs from which the header is accepted". Checking if the IP we get from a header is whitelisted?

Do you mean an app is listening to `0.0.0.0` and we'd like to check if `axum::extract::ConnectInfo` IP is e.g., `127.0.0.1`? Why can't we just make the app listen to `127.0.0.1`?...

Ok, I think I roughly understand your need. Though I think it's quite specific, as you're mention, most used proxies already have the setting on their level. Also the topic...

Yeah, I've skimmed through [the docs](https://cloud.google.com/load-balancing/docs/https#x-forwarded-for_header) and it seems to be correct: ``` X-Forwarded-For: ,, ``` > Can we add a SecureClientIpSource::XForwardedFor variant? Do you mean `SecondRightmostXForwardedFor`? I think we...

Ah, sorry, I've missed the issue header, returning multiple ips would require changing the extractor: `struct SecureClientIp(pub IpAddr)`. The current idea is to make the code work on different hosting...