9/12/2023 0 Comments Waf comodo![]() ![]() LOW - VALUED SHIPMENTS 56 CANADA 4,486 PERU 631 WAF 28,016 NY 4,855 SO AF. The iFrame tag also lines up with what Google Tag Manager gives you as well so making the change to add “https:” into the source code should not cause other problems. JAPAN 1.640 AND SCHEDULE 1 HG KONG REP NUOLA COMODO ITY DESCRIPTION UNIT. So my solution is simply to modify wp-content/plugins/wk-google-analytics/lib/Loader.php and change line 75 so it includes the “https:” as part of the url. They do have an exclusion though for Google Tag Manager iFrames but their exclusion is very specific and requires the iFrame’s src to start with: # lfd: (mod_security) mod_security (id:214540) triggered by xx.xx.xxx.xx: 5 in the last 3600 secs – Fri Jun 12 13:03:12 2020ĭoing some research this came down to the fact that ModSecurity looks for invisible iFrames, width:0 and height:0, that are also display:none. 1 and 2 for each subscription created in your Microsoft Azure cloud account. ![]() This was the error we were getting in our Firewall logs when our IP address got blocked: If the command output returns 'Disabled', as shown in the example above, the Web Application Firewall (WAF) monitoring feature is not enabled for the Microsoft Azure virtual machines (Windows and Linux) available in the selected subscription. We have been having some really odd issues with getting blocked from multiple of our sites and I have narrowed it down to ModSecurity getting triggered because of the iFrame code that is in use. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |