From 7a33ae7d77dd87d1129940bac1fb654e01981c2f Mon Sep 17 00:00:00 2001 From: David Shulman Date: Mon, 16 May 2016 10:44:18 -0700 Subject: [PATCH] Update comment about netcore50 MaxResponseHeadersLength property Windows.Web.Http is built on WinINet. There is no maximum limit (except for out of memory) for received response headers. So, returning 0 (indicating no limit) is appropriate. Fixes dotnet/corefx#8541. Commit migrated from https://github.com/dotnet/corefx/commit/9883a1064c1119eaa885e5b4cff20177f0f928fe --- .../src/netcore50/System/Net/HttpClientHandler.cs | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/libraries/System.Net.Http/src/netcore50/System/Net/HttpClientHandler.cs b/src/libraries/System.Net.Http/src/netcore50/System/Net/HttpClientHandler.cs index 1d295596af7..5173478565a 100644 --- a/src/libraries/System.Net.Http/src/netcore50/System/Net/HttpClientHandler.cs +++ b/src/libraries/System.Net.Http/src/netcore50/System/Net/HttpClientHandler.cs @@ -321,7 +321,10 @@ public long MaxRequestContentBufferSize public int MaxResponseHeadersLength { - get { return 0; } // TODO: Issue #8541 - return default value used in Wininet. + // Windows.Web.Http is built on WinINet. There is no maximum limit (except for out of memory) + // for received response headers. So, returning 0 (indicating no limit) is appropriate. + get { return 0; } + set { throw new PlatformNotSupportedException(String.Format(CultureInfo.InvariantCulture, -- GitLab