On Thu, Dec 10, 2020 at 6:32 PM Vinnie Falco via Boost-users <
boost-users@lists.boost.org> wrote:
> You can copy the code into your own source file and edit to suit your needs
>
FWIW, according to https://tools.ietf.org/html/rfc7515#appendix-C,
I can easily wrap Beast's encoder/decoder to yield
On Thu, Dec 10, 2020 at 8:56 AM Dominique Devienne via Boost-users
wrote:
> Well, what's to discuss after the above really? I'll just use something else.
You can copy the code into your own source file and edit to suit your
needs precisely, it is very small.
Thanks
__
On Thu, Dec 10, 2020 at 5:29 PM Richard Hodges via Boost-users <
boost-users@lists.boost.org> wrote:
> JWT handling seems like a natural fit within the context of Beast, and
>> although
>> this is an implementation detail, it would seem logical for decode() to
>> cope with that, no?
>>
>
> From yo
On Thu, 10 Dec 2020 at 17:10, Dominique Devienne via Boost-users <
boost-users@lists.boost.org> wrote:
> I'm decoding a Java Web Token, composed of 3 separate base64 encoded parts
> (header.payload.signature).
>
> Before I was using Boost.Serialization:
>
> using namespace boost::archive::iter
I'm decoding a Java Web Token, composed of 3 separate base64 encoded parts
(header.payload.signature).
Before I was using Boost.Serialization:
using namespace boost::archive::iterators;
using It =
transform_width, 8, 6>;
std::string tmp(It(std::begin(base64_str)), It(std::end(base64_s
