From 0f589a5b4cd9721275c99aed2607616405b92384 Mon Sep 17 00:00:00 2001
From: Pranav K <prkrishn@hotmail.com>
Date: Thu, 2 Feb 2017 14:25:36 -0800
Subject: [PATCH] Allow non-strict result for Autobahn case 4.1.3

(written by @anurse)
---
 .../AutobahnTests.cs                                            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/Microsoft.AspNetCore.WebSockets.ConformanceTest/AutobahnTests.cs b/test/Microsoft.AspNetCore.WebSockets.ConformanceTest/AutobahnTests.cs
index 76c5080286..3f0e8e0fec 100644
--- a/test/Microsoft.AspNetCore.WebSockets.ConformanceTest/AutobahnTests.cs
+++ b/test/Microsoft.AspNetCore.WebSockets.ConformanceTest/AutobahnTests.cs
@@ -72,7 +72,7 @@ namespace Microsoft.AspNetCore.WebSockets.ConformanceTest
                         // WebListener occasionally gives a non-strict response on 3.2. IIS Express seems to have the same behavior. Wonder if it's related to HttpSys?
                         // For now, just allow the non-strict response, it's not a failure.
                         await tester.DeployTestAndAddToSpec(ServerType.WebListener, ssl: false, environment: "ManagedSockets", cancellationToken: cts.Token, expectationConfig: expect => expect
-                            .OkOrNonStrict("3.2", "4.2.4"));
+                            .OkOrNonStrict("3.2", "4.1.3", "4.2.4"));
                     }
                 }