React to HttpContextFactory constructor change

- see pull aspnet/HttpAbstractions#594 and issue aspnet/HttpAbstractions#561

Author: dougbu

test/Microsoft.AspNetCore.Server.WebListener.FunctionalTests/Utilities.cs

@@ -18,23 +18,25 @@
 using System;
 using Microsoft.AspNetCore.Hosting.Server;
 using Microsoft.AspNetCore.Http;
-using Microsoft.AspNetCore.Http.Features;
 using Microsoft.AspNetCore.Http.Internal;
 using Microsoft.AspNetCore.Server.Features;
+using Microsoft.Extensions.ObjectPool;
 using Microsoft.Net.Http.Server;
 
 namespace Microsoft.AspNetCore.Server.WebListener
 {
     internal static class Utilities
     {
-        // When tests projects are run in parallel, overlapping port ranges can cause a race condition when looking for free 
-        // ports during dynamic port allocation. To avoid this, make sure the port range here is different from the range in 
+        // When tests projects are run in parallel, overlapping port ranges can cause a race condition when looking for free
+        // ports during dynamic port allocation. To avoid this, make sure the port range here is different from the range in
         // Microsoft.Net.Http.Server.
         private const int BasePort = 5001;
         private const int MaxPort = 8000;
         private static int NextPort = BasePort;
         private static object PortLock = new object();
-        private static IHttpContextFactory Factory = new HttpContextFactory(new HttpContextAccessor());
+        private static IHttpContextFactory Factory = new HttpContextFactory(
+            new DefaultObjectPoolProvider(),
+            new HttpContextAccessor());
 
         internal static IServer CreateHttpServer(out string baseAddress, RequestDelegate app)
         {