Skip to content

Commit c6beab6

Browse files
authored
Update articles/azure-web-pubsub/howto-local-debug-event-handler.md
Corrected issues reported in Acrolinx Correctness
1 parent d082458 commit c6beab6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-web-pubsub/howto-local-debug-event-handler.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Follow [Develop with local tunnel tool](./howto-web-pubsub-tunnel-tool.md) to in
3434

3535
## Debug the event handler endpoint online
3636

37-
Sometimes you might have issue sending events to configured event handler upstream, one typical error type is related to abuse protection failure, for example, `AbuseProtectionResponseInvalidStatusCode`, `AbuseProtectionResponseMissingAllowedOrigin`, or `AbuseProtectionResponseFailed`. Such error is probably related to your upstream app server settings, for example, 403 status code might be related to your app server authentication configuration, 404 status code might caused by inconsistent event handler path configured. One way to troubleshoot such failure is to send an abuse protection request to your configured event handler URL to see if it works, for example, using `curl` command to send an abuse protection request to your configured event handler URL `https://abc.web.com/eventhandler` is as below:
37+
Sometimes you might have issues sending events to a configured event handler upstream. One typical error type is related to abuse protection failure, for example, `AbuseProtectionResponseInvalidStatusCode`, `AbuseProtectionResponseMissingAllowedOrigin`, or `AbuseProtectionResponseFailed`. Such an error is probably related to your upstream app server settings, for example, 403 status code might be related to your app server authentication configuration, 404 status code might be caused by inconsistent event handler path configuration. One way to troubleshoot such failure is to send an abuse protection request to your configured event handler URL to see if it works, for example, using `curl` command to send an abuse protection request to your configured event handler URL `https://abc.web.com/eventhandler` is as below:
3838

3939
```bash
4040
curl https://abc.web.com/eventhandler -X OPTIONS -H "WebHook-Request-Origin: *" -H "ce-awpsversion: 1.0" --ssl-no-revoke -i

0 commit comments

Comments
 (0)