Mohammad Nejati

Addressed in https://github.com/boostorg/beast/pull/2019.

Addressed in https://github.com/boostorg/beast/pull/2808.

> This issue is still marked as open despite #2611 being merged with the description saying it closes this issue. Is this still considered open? I believe the issue has...

I believe so (and did some tests). Could you confirm, @klemens-morgenstern?

Addressed in https://github.com/boostorg/beast/commit/4ff4c79d5b3df7a56e692f6112de48bdc33a549f, by adding `BOOST_BEAST_FILE_BUFFER_SIZE` preprocessor definition that allows setting buffer size for the file_body. There is an open issue for making the `buffer_size` dynamically reconfigurable: https://github.com/boostorg/beast/issues/1094.

Addressed in https://github.com/boostorg/beast/pull/2787.

Closing this pull request as: - The `json_body` example has already been added in https://github.com/boostorg/beast/pull/2511. - The `http_client_sync_post` example is too complex to be considered a suitable example.

@Yinpinghua Is this still open?

Could you please provide a minimal, reproducible code? I have no idea what the problem is, as the provided code doesn't reveal any issues.

Fixed in https://github.com/boostorg/beast/commit/ca824f607ccab6682b955eb91ed49753e6433069 and https://github.com/boostorg/beast/commit/925043e1e8df7474165f23c9a60223b0ab886be4. Mentioned in the CHANGELOG: https://github.com/boostorg/beast/blob/d0dd9c50694bcbb8836775e780eb046f66b3e1d7/CHANGELOG.md?plain=1#L157