v1.6.1

Warning

v1.6.0 / v1.6.1 do not work with Traefik right now due to an upstream issue with Traefik’s plugin catalog (plugin integrity check failure). We’re working with Traefik to get this resolved as soon as possible. Please use v1.5.0 until further notice.

What's Changed

• Add support for custom error responses when unauthorized
• Add support for Pangolin (>= 1.22.0) AI Gateway public resources

Full Changelog: v1.5.0...v1.6.1

v1.6.0

Warning

v1.6.0 / v1.6.1 do not work with Traefik right now due to an upstream issue with Traefik’s plugin catalog (plugin integrity check failure). We’re working with Traefik to get this resolved as soon as possible. Please use v1.5.0 until further notice.

What's Changed

• Add support for custom error responses when unauthorized
• Add support for Pangolin (>= 1.22.0) AI Gateway public resources

Full Changelog: v1.5.0...v1.6.0

v1.5.0

What's Changed

• Strip p_token access token query param when persistent access token mode is enabled

Full Changelog: v1.4.1...v1.5.0

v1.4.1

What's Changed

• Update information passed downstream

Full Changelog: v1.4.0...v1.4.1

v1.4.0

What's Changed

• Add strip session token information from the request

Full Changelog: v1.3.1...v1.4.0

v1.3.1

What's Changed

• Add send Badger version to Pangolin for verify-session

Full Changelog: v1.3.0...v1.3.1

v1.3.0

What's Changed

• Add support for Cloudflare proxy real IP headers to get client IP addresses when behind Cloudflare proxy
• Add support for custom trusted proxy headers to get client IP addresses when behind a trusted proxy other than Cloudflare proxy
• Add Remote-Role header to Badger passthrough headers
• Add throw a 401 redirect as necessary for the header auth to prompt the browser for a user and password

Full Changelog: v1.2.1...v1.3.0

Cloudflare Proxy Real IP Support

This release improves how Badger determines the real client IP when requests pass through proxies.

Badger 1.3.0 now automatically supports Cloudflare by trusting Cloudflare IP ranges and extracting the client IP from the CF-Connecting-IP header, ensuring accurate IPs for rate limiting, logging, geoblocking, and downstream services without extra configuration.

It also adds support for non-Cloudflare setups. You can now define custom trusted proxy IP ranges and specify a custom header to extract the client IP, making Badger usable behind any trusted load balancer or reverse proxy.

For more information about how this works read the README.
For how this works with Pangolin, read the Pangolin Docs.

v1.2.1

What's Changed

• Always set Remote-* headers

Full Changelog: v1.2.0...v1.2.1

v1.2.0

What's Changed

• Add auth headers to request

New Contributors

• @pyrho made their first contribution in #7

Full Changelog: v1.1.0...v1.2.0

v1.1.0

What's Changed

• Pass all headers and query params in verify-session request body
• Apply response headers to http response
• Remove accessTokenQueryParam
  • Access token check is now performed by third party in verify-session request

Full Changelog: v1.0.0...v1.1.0