request.prepare_payload() 1.67 about beast HOT 5 CLOSED

When you call prepare_payload(), the Content-Length and Transfer-Encoding field values are automatically adjusted based on the message body.

For instance:

http::request<http::string_body> req;
req.method(beast::http::verb::post);
req.body() = "body-contents";
req.prepare_payload(); // Content-Length set based on the body

Typically, you won't need to explicitly set Content-Length. However, if necessary, you can bypass calling prepare_payload(), and the values set in Content-Length and Transfer-Encoding will remain unchanged.

from beast.

When you call prepare_payload(), the Content-Length and Transfer-Encoding field values are automatically adjusted based on the message body.

For instance:

http::request<http::string_body> req;
req.method(beast::http::verb::post);
req.body() = "body-contents";
req.prepare_payload(); // Content-Length set based on the body

Typically, you won't need to explicitly set Content-Length. However, if necessary, you can bypass calling prepare_payload(), and the values set in Content-Length and Transfer-Encoding will remain unchanged.

Yes - thank you!

I am aware of this and we could ignore the line to set content-length even - but prepare_paylod seems to be ignoring the size of my body when I have it formatted in a json style

from beast.

If this is how you are setting the message body, it is incorrect:

req.set(http::field::body, "{\"username\":\"admin\", \"password\":\"admin"}");

You are actually setting a header field there.

This is how we set body content (assuming you are using http::request<http::string_body>):

req.body() = "body-contents";

from beast.

HAHA okay that explains so much - that resolves my issue thank you hahaha

from beast.

Issue resolved

from beast.