tree 87c662fb280bb34e8464c1f5a15d51c45c756a4f
parent 9062d478d4dc89598e215e1538ba8fbb8db2cf10
author Andrew Geissler <geissonator@yahoo.com> 1633721761 -0500
committer Ed Tanous <ed@tanous.net> 1637095004 +0000

reduce error traces in connection and auth code

These logs are reported in good paths (at least web interfaces are
working fine when they are logged). Convert them to warnings so they do
not show up as false errors when debugging bmcweb.

Here's the log we were getting:
Oct 08 19:20:48 p10bmc bmcweb[15348]: (2021-10-08 19:20:48) [ERROR "http_connection.hpp":537] 0x14bd360 Error while reading: end of stream
Oct 08 19:20:48 p10bmc bmcweb[15348]: (2021-10-08 19:20:48) [ERROR "http_connection.hpp":531] 0x14910b0 async_read_header 308 Bytes
Oct 08 19:20:48 p10bmc bmcweb[15348]: (2021-10-08 19:20:48) [ERROR "authorization.hpp":292] authHeader=

These code paths, and why they are not real errors, is not totally clear
to me. Hoping for some discussion on it in this review.

Tested:
- Verified these no longer show up when doing basic system management
  with just error traces enabled in bmcweb

Change-Id: If357aeb93ff28ef02e135a888524e057cb188871
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>