beast
beast copied to clipboard
HTTP and WebSocket built on Boost.Asio in C++11
There should be an example of use: ``` request req; ... std::cout
This section should discuss the security considerations for HTTP users. * Slow loris mitigation * Header smuggling mitigation >Also stuff like buffer overruns or integer overflows are common they are...
Which smaller design choices deserve an explicit rationale in the documentation?
Documentation and javadocs should refer to "the associated executor" when stating execution guarantees.
The documentation for some basic_fields members should note that certain previously returned string_views are invalidated. For example erasing a field will invalidate any previously returned string views to that field's...
```read``` or ```async_read``` operations may require "large" amounts of stack. The documentation should acknowledge this. Example: https://github.com/boostorg/beast/blob/ffbe65f4c922e1b8d76e85434d0a8d3ee1c083e9/include/boost/beast/http/impl/basic_parser.ipp#L486 If the parser is used inside of a stackful coroutine, this may easily...
The wording should make it clear that the only observable effects of modifiers are in the serialized output and return values from observers. And it should be stated explicitly that...
Hi, thank you for the great project. I'd like to propose simple feature, namely add `file_body::value_type::reset()` overload that takes `file_size` as an extra parameter. This would allow saving one syscall...
Call sites can just use `static_cast`, this function doesn't add much and probably won't survive in a TS.
Error messages should be verbose and helpful for the developer instead of terse.