Closed troyxmccall closed 1 year ago
omg, so sorry, i meant to make this on my own fork, it's late, i apologize
Haha! No issue @troyxmccall, I'd still take a look at the improvement you made.
Although you should never cache the Authroization
header as someone else who's making a request might end up with someone else's Authorization
header value. (Stealing the JWT of someone else...)
@acouvreur excellent catch, ty! Will update my fork to have a blacklist of headers that can never be cached
caching layer allows for custom turning so you can override defaults
note: keeping tags from origin
some benchmarks on bare-metal
1) hitting
whoami
hooked directly into traefik (no middleware) - this is our benchmark2a) origin's response time with 200's (modsecurity layer activated)
2b) origin's response time with 4xx ((modsecurity layer activated))
3a) our layer, just with alpine and http transport (no-caching) with 200's (modsecurity layer activated)
3b) our layer, just with alpine and http transport (no-caching) with 4xx (modsecurity layer activated)
4a) our layer, with full caching, with 200's (modsecurity layer activated):
4b) our layer, with full caching, with 4xx (modsecurity layer activated):
rough summary compared to baseline: