← Back to context Comment by nicoledevillers 10 months 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 10 months 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 10 months ago i don't speak for substack, but i do work there and changed the WAF rule :) silverwind 10 months ago Why not review rules before applying them?
SonOfLilit 10 months 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 10 months ago i don't speak for substack, but i do work there and changed the WAF rule :)
nicoledevillers 10 months 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?