Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider 4xx and 5xx as failures #295

Merged

Conversation

jgogstad
Copy link
Contributor

Redirects shouldn't be considered failures, as reported in #281

@msftclas
Copy link

Hi @jgogstad, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@@ -117,7 +117,7 @@ public void onEndRequest(ServletRequest req, ServletResponse res) {

ApplicationInsightsHttpResponseWrapper response = ((ApplicationInsightsHttpResponseWrapper)res);
if (response != null) {
telemetry.setSuccess(response.getStatus() >= 200 && response.getStatus() < 300);
telemetry.setSuccess(response.getStatus() < 400);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution.
I see the .NET SDK also treat 401 as success

Please keep the same behavior so the SDKs are aligned. Thanks.

@OriYosefiMSFT OriYosefiMSFT merged commit 91c966d into microsoft:master Jul 29, 2016
@OriYosefiMSFT
Copy link
Member

I will add another commit to identify 401 as success

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants