Just using a prepared statement to add it to the users table
Just using a prepared statement to add it to the users table
T
CHashed passwords using the password_hash() function that php has
C@az
IYou should be fine if you're properly using prepared statements.
IAssuming that those random strings are supposed to be user emails, I'd also try to validate that they're valid emails before inserting into the DB.
KStrange ISP you have
R¯\_(ツ)_/¯
KDoes it make sense to cache pages like this https://akami-solutions.cc/akami-cgi/icon/envelope ? Because CloudFlare doesnt think so :0010shiba_think:
Kme: cloudflare.com
My Fingers: cloudfl.re
My Fingers: cloudfl.re
H
THi everyone. Does anyone have any idea why cloudflare ignored my WAF rules? This is the request and these are my rules:
Tbased on the rules shouldn't the request be blocked?
Tit was a request with HTTP1.0
HIt's because you have Bot Fight Mode enabled. Bot Fight Mode bypasses your rules
Tyes, but based on their traffic sequence shouldn't after bot fight mode pass through WAF? At least this is what I understand from this top to down sequence
KNo wonder why CloudFlare Dashboard has everytime loading issues. Its made with React I guess :NayaDerp:
HNot quite. If you use SuperBotFightMode, then yes, but regular BFM overrides all your rules
HIt's generally a heavy hammer, so we recommend only using it when absolutely necessary, or otherwise upgrading to get SBFM
Tokay, I understand about BFM and SBFM but what do you mean by absolutely necessary? When is it necessary to activate BFM? (I am new to managing DNSes) 
JHow can I configure Cloudflare to allow my IP address to bypass a 301 redirect set by Page Rules and load files directly from the hosting server?
Yesterday, I successfully configured the redirect rule setting to allow my IP address to bypass the 301 redirect. However, I had to delete all settings this morning and start fresh. I can't remember how I did it yesterday. How can I make my IP address bypass the 301 redirect instructions set under page rules?
Thanks.
Yesterday, I successfully configured the redirect rule setting to allow my IP address to bypass the 301 redirect. However, I had to delete all settings this morning and start fresh. I can't remember how I did it yesterday. How can I make my IP address bypass the 301 redirect instructions set under page rules?
Thanks.
HBasically, only use BFM when you are currently under attack by a lot of bots. It isn't something I would recommend having on all the time
HAdd an
AND condition to your rule, where if IP Source Address does not equal your IPJSo if I set a Redirect Rule with this condition, should I delete the 301 instructions under Page Rules?
TIf I understood correctly it is better to have WAF rules to filter traffic rather than activating the bot mode . Do you happen to have any sheet with what WAF rules I should have (except the ones I've showed in the image above)?
. Do you happen to have any sheet with what WAF rules I should have (except the ones I've showed in the image above)?TAt least the basic ones
HYou can do that
HI do not, unfortunately
Tokay, thank you for the answers :MeowHeartCloudflare:
VWhy Cloudflare is slow in India?
A simple
A simple
GET request with D1 Select * from Users Limit 10 take 1690ms to load.
VAPAC region for DB. How to find what what pop i am hitting in the rays?
V
VBOM - I guess Bombay, India
KBombe :BL_Boom:
VGot it, thanks for the knowledge sharing. Now I know it better.
JThank You for the insight, it worked.
HIt does not appear to be supported
HAs it isn't on the Available Soon list, I wouldn't hold my breath
TDoes someone know if the "known bots" from WAF rules includes verified bots mentioned here https://radar.cloudflare.com/traffic/verified-bots ?
HIt should be the exact same, yeah
Tokay, thank you
T:MeowHeartCloudflare:
EQuick question if anyone has a moment? I'm assuming DNS records are the issue is www works but non www doesn't work for my website?
DThanks
Pis it true that cache rule work bottom to top?
CCCache Rules are stackable. This means that multiple matching rules can be combined and applied to the same request. For example, if multiple cache rules match the same URL, then the features set in those cache rules will all be applied in order. If several matching rules set a value for the same setting, the value in the last matching rule wins. For an example of a similar scenario where multiple rules match, refer to the Origin Rules FAQ.
For conflicting settings (for example, bypass cache versus eligible for cache), the last matching rule wins. For example, if cache rule #1 is set to cache everything on example.com/images and cache rule #2 is set to bypass cache on example.com, then cache will be bypassed for all URLs that match example.com, since rule #2 is the last matching rule.
