Is your feature request related to a problem? Please describe.
Only the reverse proxy usage adds the X-Anubis-Rule and X-Anubis-Action header to the request. If I use the /x/cmd/anubis/api/check endpoint I don't receive any information about which rule and action was applied. Which makes it hard to debug why a certain request was challenged, denied or allowed.
Solution you would like.
Just add the same headers to the /x/cmd/anubis/api/check response.
Alternatively (the ultimate solution) if I request with accept: application/json give me back a detailed check protocol that contains all rules that got triggered and the final action including the weigh. Currently all this information is only accessible via the debug logs which we don't have enabled in production as this would mean an increase in logging costs and additional work to correlate Anubis logs with our app logs.
Describe alternatives you have considered.
No response
Additional context
No response