Today at 12:00 I changed the DNS Entry to point to an Application Gateway instead of Azure Frontdoor. After doing that there were some failures with status code 0. The funny thing is that only POST requests were blocked. GET and Option Requests sitll worked fine. Also in the log the Application Gateway didn’t seem to resolve the route to the server. The question is whether this behavior is a client side firewall issue or actually a problem with the App Gateway.

Facts:
Application Gateway WAFv2 with WAF on detection mode
Routes to App Services behind.
Post requests receive Status Code 0 with 0 bytes and no request headers for some clients
Get and Options requests work on all clients
Occured 2-3 hours after change

Is there any logical explaination for this behavior?