This is part of a scenario set. You have an Azure Application Gateway with Web Application Firewall (WAF) enabled. The gateway is configured to route requests to the gateway's own URL. When you attempt to browse the URL you get an HTTP 403 response. Diagnostics show the traffic is blocked by a WAF rule with ruleId 920300. To make the URL accessible through the Application Gateway, you disable the WAF rule with ruleId 920300. Does this change achieve the goal?

Yes, disabling the specific WAF rule (920300) that is blocking the traffic will resolve the HTTP 403 error and make the URL accessible through the Application Gateway. Rule 920300 is part of the OWASP ModSecurity Core Rule Set (CRS) and typically relates to detecting remote command execution attempts or other malicious input patterns. When the Application Gateway is routing requests to its own URL, it can sometimes trigger WAF rules due to the nature of the request or the URL itself being interpreted as suspicious by the WAF. By disabling the rule, you are allowing the traffic that was previously identified as a threat by that specific rule to pass through.