Aggregation: Increase response read limit to 50MB

With Redfish aggregation, responses from satellite BMCs can be on the
order of MBs due to use cases like logging or binary payloads.
Offloading $expand could similar result in responses that exceed the
current read limit of 128 KB.

Splits the connection pools used for aggregation and EventService so
that the response read limit is 50MB for responses associated with
aggregation.  Pools used by EventService keep the current limit of 2^17
bytes or 128 KB.  It also propogates a ConnectionPolicy object that gets
instantiated within HttpClient, which allows per-client policies for
retry/byte limits.  This allows EventService and aggregation to have
different policies.

Tested:
With aggregation enabled I was able to return a response from a
satellite BMC which was than 2MB.  Ran the Redfish Mockup Creator and it
was able to successfully query all aggregated resources as part of
walking the tree.  Also verified that HTTP push events still work with
EventListener.

Change-Id: I91de6f82aadf8ad6f7bc3f58dfa0d14c0759dd47
Signed-off-by: Carson Labrado <clabrado@google.com>
Signed-off-by: Ed Tanous <edtanous@google.com>

1 files changed, 0 insertions, 3 deletions

diff --git a/src/webserver_main.cpp b/src/webserver_main.cpp
index 8e3a6f4ca9..b13ab270ec 100644
--- a/src/webserver_main.cpp
+++ b/src/webserver_main.cpp
@@ -86,9 +86,6 @@ static int run()
 #ifdef BMCWEB_ENABLE_REDFISH
     redfish::RedfishService redfish(app);
 
-    // Create HttpClient instance and initialize Config
-    crow::HttpClient::getInstance();
-
     // Create EventServiceManager instance and initialize Config
     redfish::EventServiceManager::getInstance();