Replies: 1 comment 3 replies
-
There's a lot of caching internally for entries and indexes, but not for the actual HTTP responses. The work to disable anonymous queries would avoid a lot of the bandwidth-related risk. For caching, we'd need to implement ETag headers and support HEAD requests for the endpoints, which is not a bad idea, but wouldn't be a high priority for at least a release or two. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
I wonder if we could have (already have?) a native cache for
/v1/(person|group)
handlers?On my setup they dump circa 200/100kB and as such are IMO certainly open to kinda DDOS.
If it's not relevant to Kani per se, what could be a hook to invalidate external cache?
TIA
Beta Was this translation helpful? Give feedback.
All reactions