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/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,