Mohammad Nejati
Mohammad Nejati
Thanks for reporting, The problem is that the generated CSV file uses `\r\n` as the newline character, and the last column would include `\r`. For example, in this case, it...
It seems that when BOOST_ASIO_USE_TS_EXECUTOR_AS_DEFAULT is defined, Asio utilizes the executor as the any_completion_executor type: https://github.com/chriskohlhoff/asio/blob/fa27820c05afd740fa2adc1ecfb9da5afe026443/asio/include/asio/any_completion_executor.hpp#L31 However, when it attempts to use the noexcept constructor of any_completion_executor : https://github.com/chriskohlhoff/asio/blob/fa27820c05afd740fa2adc1ecfb9da5afe026443/asio/include/asio/any_completion_handler.hpp#L120 since...
No, I don't have access to that.
> I've just read in the documentation that for the async operations we have to use a handler. As you mentioned above, CloseHandler may be good, but as @rdzienis said,...
@ecorm No, there is no support for specifying a range in basic_file_body. However we can add this if you have a use case for it.
In which line does it hang? Are you certain about the server-side; does it respond with a proper HTTP response after receiving the 2GB request? If it blocks in the...
I'm unable to replicate this issue on my end. Could you please provide the server-side code?
The issue arises from the narrowing conversion occurring in [this line of code](https://github.com/chriskohlhoff/asio/blob/ed5db1b50136bace796062c1a6eab0df9a74f8fa/asio/include/asio/detail/impl/socket_ops.ipp#L1386 ) in Asio, which converts `bytes_transferred` (which is of type `unsigned int`) to `signed_size_type` (a type alias...
Yes, indeed, all variations of HTTP write operations encounter the same issue as they utilize `async_write_some` and `write_some` on the provided stream. I raised an issue on Asio repository: https://github.com/chriskohlhoff/asio/issues/1443...
I would suggest using [http::serializer::limit](https://www.boost.org/doc/libs/1_85_0/libs/beast/doc/html/beast/ref/boost__beast__http__serializer/limit.html) to set a limit on the size of the returned `BufferSequence` (note that this is different from `body_limit` and doesn't affect the maximum message size...