Last edited by DrByte; 30 Jun 2016 at 03:55 AM. Reason: edited
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
Ya, it probably is. But for the "html" tag to be treated as "SQLmop"seems odd. Nevertheless, at least it's unlikely that you'll be planning to keep all that demo text in your pages.
That's something on our end, which also peeks at the html and head stuff. But at least it's not throwing a 403 :)
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Thanks again. You are right, the demo data will be removed when I get to the point ready to import my v154 database.
Host says the rule is disabled but no explanation of why I still receive it. It is probably best that I just drop the case before the fingerpointing or peeing contest begins.
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
I am also having the 403 error.
I have 2 EZ-Pages that give me that error without changing anything and just clicking UPDATE.
Both of these pages have been fine since 1 week ago. No other changes have been made.
The server folks say, You can let them know it's triggering an Apache mod_security alert due to the "content="text/html;" in the meta tag.
I hope this doesn't turn into a finger pointing game!
In my EZ-Pages content I had <html> at the beginning and </html> at the end.
When I removed these the problem is fixed.
I no longer get the 403 error.
Why would this cause a problem?
Bookmarks