Skip to content
Discussion options

You must be logged in to vote

Hi @amddeus,

This sounds exactly like Issue #1247, where Anubis falsely triggers a browser verification challenge on media requests (specifically GIFs/videos), causing playback to fail.

The root cause often appears to be the Range header sent by the browser/player. For some reason, this triggers the WAF rules in Anubis for certain content types.

The Workaround:
If you are running Caddy in front of Anubis (or Redlib), you can try stripping the Range header from the request before it reaches the backend. This forces the server to send the full file (200 OK) instead of partial content (206), which usually bypasses the issue for short clips.

Add header_up -Range to your Caddyfile's reverse_pr…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by amddeus
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants