[ad_1]
After enabling the Web Application Firewall in a development Power Pages site, some developers reported that some web API queries using FetchXML stopped working, throwing a 403 error.
After running some tests to validate the issue, it turned out that WAF was detecting them as an attack. This blog post details how the query was written and what we need to do to fix it.
Troubleshooting
The first step was to identify what queries were failing. In the example below, the query that always worked fine suddenly stopped working after enabling WAF:
Opening the request in a new tab, we can see the request has been blocked (from what looks to be a WAF message):
So the first thought was to look at the WAF logs and see if there was any warning message (we can Download them from the WAF config section in Design Studio):
On the downloaded log, I could find information related to that request:
Looking at the message, one of the default rules from WAF blocked the…
[ad_2]
Source link