grapland
grapland
in `example/cpp20_intro_tls.cpp`, it does ``` conn->next_layer().set_verify_mode(asio::ssl::verify_peer); conn->next_layer().set_verify_callback(verify_certificate); ``` before `async_exec`. I wonder whether this survives auto-reconnect? If not, where should I reinstate these for new connections?
It always constuct a system-default ssl context which uses system common CA set and no client certificate (for mutual authentation at server side).
The cat generally has 3-5 different gaits. Here is a demo for dog, but still works for cat: https://www.youtube.com/watch?v=AZGNjKolAiQ
boost version: 1.78 compiler: gcc version 11.2.0 typical stack trace: ``` #0 boost::iostreams::non_blocking_adapter::write (n=4096, s=0x556a785d1000 "R`G\312 X\355\231r\220\256\306\257\022\202\065%W\261\260\342\236\245\277\277\364\332\240\320\253\253\037d\256\256V\036\256v.Ko\315w\326\360\261?\027\304\276\346\066\367\347\364>\257\177-\037+\354S\001$K\320g?\342\353 XmE=\004k\354l`a\357\177{\303\323\235\210}R(\373$\252\004/\302\344\337D\261\350\\rF\370\203\255\335\210}\006\215C_\035\264y\343y\207\v\367\371\265\035.\253,\003\220[\\D\226s\311\371G\217\060\347\342\312\346|\326\321\210\340\263\237\034}\354V\324 \334\246\303|\237~\267\300ns\335D\026\327x\\\207\335{?~\345b\304\264\200\337\345\315\303\214W\264\027\037tq\233\373\256"..., this=0x7ffc25e00910) at /usr/local/include/boost/iostreams/detail/adapter/non_blocking_adapter.hpp:41 #1 boost::iostreams::detail::write_device_impl::write (n=, s=, t=..., t=..., s=, n=)...
For instance, for json content ```json {"value": 1.23456789234567892345678923456789234567892345678923456789} ``` I'd like to get a string-like `1.23456789234567892345678923456789234567892345678923456789` from parsed `value`. This is useful not even for arbitrary precision floats, but for...