Skip to content

Commit 97e7cad

Browse files
authored
Merge pull request #113084 from mrbullwinkle/mrb_04_28_2020_ip_exceptions
add supportability update
2 parents 9eb981f + a0415dd commit 97e7cad

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/azure-monitor/app/troubleshoot-availability.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Troubleshoot web tests in Azure Application Insights. Get alerts if
44
ms.topic: conceptual
55
author: lgayhardt
66
ms.author: lagayhar
7-
ms.date: 09/19/2019
7+
ms.date: 04/28/2020
88

99
ms.reviewer: sdash
1010
---
@@ -64,6 +64,10 @@ Check the classic alerts configuration to confirm your email is directly listed,
6464

6565
Check to ensure the application receiving the webhook notification is available, and successfully processes the webhook requests. See [this](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitor-alerts-unified-log-webhook) for more information.
6666

67+
### I am getting 403 Forbidden errors, what does this mean?
68+
69+
This error indicates that you need to add firewall exceptions to allow the availability agents to test your target url. For a full list of agent IP addresses to allow, consult the [IP exception article](https://docs.microsoft.com/azure/azure-monitor/app/ip-addresses#availability-tests).
70+
6771
### Intermittent test failure with a protocol violation error?
6872

6973
The error ("protocol violation..CR must be followed by LF") indicates an issue with the server (or dependencies). This happens when malformed headers are set in the response. It can be caused by load balancers or CDNs. Specifically, some headers might not be using CRLF to indicate end of line, which violates the HTTP specification and therefore fail validation at the .NET WebRequest level. Inspect the response to spot headers, which might be in violation.

0 commit comments

Comments
 (0)