[meta] breakage caused by imperva/incapsula
Categories
(Web Compatibility :: Knowledge Base, defect)
Tracking
(Not tracked)
People
(Reporter: ksenia, Unassigned)
References
(Blocks 6 open bugs)
Details
(Keywords: meta, webcompat:contact-in-progress, webcompat:site-report)
User Story
outreach-assignee:ksy36 outreach-contact-date:2026-01-30 outreach-response-date:2026-01-30
A meta bug to track site breakage caused by Incapsula/Imperva firewall
|
||
Comment 1•18 days ago
|
||
ni? myself for outreach, this is getting to a level that's incident-worthy.
|
||
Comment 2•10 days ago
|
||
I contracted Imperva Cloud WAF support and they are responsive, and tested things with Firefox.
For bug 1998019 they stated "Expected ACL error".
For bug 2000009 they did not manage to reproduce (this matches :gerard-majax experience in the bug that it was intermittent)
For bug 2001341, bug 2011435 and bug 2011861 they did not reproduce.
For bug 2010547 they confirm, but state the the error is returned by the site's JS, not their firewall.
Do we have any very recent active cases we can point to?
|
||
Comment 3•9 days ago
|
||
So that means 1998019 should be moved to needscontact if the site owners configured their firewall to block firefox on purpose...
|
||
Comment 4•9 days ago
|
||
(In reply to Gian-Carlo Pascutto [:gcp] from comment #2)
I contracted Imperva Cloud WAF support and they are responsive, and tested things with Firefox.
[...]
For bug 2000009 they did not manage to reproduce (this matches :gerard-majax experience in the bug that it was intermittent)
For me it was permanent issue, on multiple devices, for several days. And when I started filing a support message I tested with release and then chromium and things started to work a few minutes after.
|
|
||
Comment 5•6 days ago
|
||
Ksenia is doing the outreach here, updating the flags accordingly.
Description
•