v0.6.1

Impl some std traits

Full Changelog: v0.6.0...v0.6.1

CloudFront-Viewer-Address

What's Changed

• feat: Support obtaining client IP from CloudFront-Viewer-Address header by @jreppnow in #28

New Contributors

• @jreppnow made their first contribution in #28

Full Changelog: v0.5.1...v0.6.0

v0.5.1

What's Changed

• provide FromStr impl for SecureClientIpSource by @maxcountryman in #25

New Contributors

• @maxcountryman made their first contribution in #25

Full Changelog: v0.5.0...v0.5.1

Axum-0.7

What's Changed

• Disable unused axum features by @paolobarbolini in #20
• Bump axum to 0.7.1 by @cole-h in #21

New Contributors

• @paolobarbolini made their first contribution in #20
• @cole-h made their first contribution in #21

Full Changelog: v0.4.2...v0.5.0

Public `InsecureClientIp::from` and `SecureClientIp::from`

What's Changed

• doc: when FlyClientIP is run on health check path provide header by @64bit in #16
• docs: fix typo by @Colerar in #17
• feat: public from api by @Colerar in #19

New Contributors

• @64bit made their first contribution in #16
• @Colerar made their first contribution in #17

Full Changelog: v0.4.1...v0.4.2

Fix docs links to examples

v0.4.1

Fix docs links to examples

Secure and Insecure client IPs

The API has been split into two parts: SecureClientIp and InsecureClientIp.

If you're happy with the previous behaviour just use InsecureClientIp instead of ClientIp extractor.

But if you care even a bit about potential spoofing, take a look at the README to understand the defference between "secure" and "insecure" options.

Use the last IP from `X-Forwarded-For` header

A bugfix release - it's now uses the last IP from the X-Forwarded-For header.
Thank you @dae 🙏

Adapt for axum 0.6

Thank you @kavin-kr 🙏

Adapt for axum 0.5

Thank you, @dalloriam 🙏