[Boost-users] Boost.Beast includes CRLF in HTTP fields

Subject: [Boost-users] Boost.Beast includes CRLF in HTTP fields
From: David Demelier (markand_at_[hidden])
Date: 2018-07-06 10:45:23

Hello,

It looks like HTTP response headers are saved with trailing CRLF in the
message upon receiption after (async_)read.

Since it usually does not add additional valuable information, would it
be possible to remove them in next version of Boost.Beast? It will be
more convenient as you don't need to trim them when you want to capture
the field value.

Regards,

-- 
David