middleware onBefore is adding multiple Bearer tokens after initial request fails with 401

[leandemon]

When onFailure processes a 401 status code it adds a Bearer token (using $request->withHeader), then onBefore also adds a Bearer token but uses $request->withAddedHeader which effectively creates an Authorization Header that's got 2 duplicate Bearer tokens in it, causing authentication to fail.

Here's the Authorization header that actually gets sent:
Authorization: Bearer 5b3df637e24ace993fc5eb87967db5be92fc35df, Bearer 5b3df637e24ace993fc5eb87967db5be92fc35df

Looks like $request->withAddedHeader simply needs to be changed to $request->withHeader

[jsacksick]

Just experienced the same today... And lost hours due to this... (I know this got created almost 5 years ago, but figured I'd mention it).

[grambas]

Some issue for me

[grambas]

There is already PR for that: #23
Can anybody merge it?