I agree. Removing the blacklist was a BAD idea. Can we expect this feature to return in 2.5? To me, this is a must have feature as it helps reduce site attack exposure
Hi, I'm using Cloudflare to accelerate, it works smoothly with nopcommerce22, but all access ip has been shifted to Clouldflare's IP. I found the below words from Cloudflare to explain how to get original IP.
"Please change the string as below:
// Old way of getting the IP Address string IPAddress = Request.UserHostAddress;
// New way based on the http headers string IPAddress = Request.Headers["CF-Connecting-IP"];
(If you're using ASP classic: Request.ServerVariables("CF-Connecting-IP") )"
Anybody let me know where to modify at nopcommerce22? thanks a lot!
Can we expect this feature to return in 2.5? No, it's not planned for version 2.5. The task status is proposed (not active).
Is there any way to block malicious users to register themselves in the nopCommerce site? They normally use invalid email addresses such as "[email protected]." Is it possible to reject their registering by ip address blocking?
Can we expect this feature to return in 2.5? No, it's not planned for version 2.5. The task status is proposed (not active).
Is there any way to block malicious users to register themselves in the nopCommerce site? They normally use invalid email addresses such as "[email protected]." Is it possible to reject their registering by ip address blocking?
Can we expect this feature to return in 2.5? No, it's not planned for version 2.5. The task status is proposed (not active).
Is there any way to block malicious users to register themselves in the nopCommerce site? They normally use invalid email addresses such as "[email protected]." Is it possible to reject their registering by ip address blocking? Have you tried Captcha in register page?
No, I have not. Thank you for your advice. I think it will be effective for blocking malicious registering by program. By the way, I found that "<rewrite><rules>" ip address blocking is also effective.