Skip to content

Commit 55f195a

Browse files
authored
Fix two sentences in troubleshoot-subscription-validation.md
In this proposal, I am submitting changes to make the documentation of troubleshooting Azure event grid subscription cleaner.
1 parent 1b176f7 commit 55f195a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/event-grid/troubleshoot-subscription-validation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ During event subscription creation, if you're seeing an error message such as `T
1111

1212
- Do an HTTP POST to your webhook url with a [sample SubscriptionValidationEvent](end-point-validation-event-grid-events-schema.md#validation-details) request body using curl or similar tool.
1313
- If your webhook is implementing synchronous validation handshake mechanism, verify that the ValidationCode is returned as part of the response.
14-
- If your webhook is implementing asynchronous validation handshake mechanism, verify that you're the HTTP POST is returning 200 OK.
15-
- If your webhook is returning `403 (Forbidden)` in the response, check if your webhook is behind an Azure Application Gateway or Web Application Firewall. If it is, then your need to disable these firewall rules and do an HTTP POST again:
14+
- If your webhook is implementing asynchronous validation handshake mechanism, verify that your POST endpoint is returning 200 OK.
15+
- If your webhook is returning `403 (Forbidden)` in the response, check if your webhook is behind an Azure Application Gateway or Web Application Firewall. If it is, then you need to disable these firewall rules and do an HTTP POST again:
1616
- 920300 (Request missing an accept header)
1717
- 942430 (Restricted SQL character anomaly detection (args): # of special characters exceeded (12))
1818
- 920230 (Multiple URL encoding detected)

0 commit comments

Comments
 (0)