This will fix a bug that wasn't properly removing the BEARER argument when parsing the token. When I was testing with one method, it was presented as BEARER and it seems that now it can also be Bearer! Given that we can't predict capitalization, the updated strategy is to just split the string into two pieces, and take the second half (the token).
This will fix a bug that wasn't properly removing the BEARER argument when parsing the token. When I was testing with one method, it was presented as BEARER and it seems that now it can also be Bearer! Given that we can't predict capitalization, the updated strategy is to just split the string into two pieces, and take the second half (the token).
This will close #247