← Back to context Comment by nicoledevillers 1 day ago it was a cf managed waf rule for a vulnerability that doesn't apply to us. we've disabled it. 3 comments nicoledevillers Reply SonOfLilit 1 day ago This comment deserves to be much higher, assuming this user speaks for Substack (no previous submissions or comments, but the comment implies it). nicoledevillers 1 day ago i don't speak for substack, but i do work there and changed the WAF rule :) silverwind 21 hours ago Why not review rules before applying them?
SonOfLilit 1 day ago This comment deserves to be much higher, assuming this user speaks for Substack (no previous submissions or comments, but the comment implies it). nicoledevillers 1 day ago i don't speak for substack, but i do work there and changed the WAF rule :)
nicoledevillers 1 day ago i don't speak for substack, but i do work there and changed the WAF rule :)
This comment deserves to be much higher, assuming this user speaks for Substack (no previous submissions or comments, but the comment implies it).
i don't speak for substack, but i do work there and changed the WAF rule :)
Why not review rules before applying them?