Marten Gajda

Good point about `SimpleUrlEncodedValuePairs` and `StructuredStringFragment`. Although the implementations are different, the results is basically the same. The only exception is that for some reason `SimpleUrlEncodedValuePairs` skips the very first...

Yep. Also rename `BearerAuthRequestDecorator` to `BearerAuthenticatedRequest` as discussed (please also update the example in README.md when you do so).

Thanks for the report. Please tell me, what exactly means "empty response"? Are we talking about a valid HTTP response or an invalid one? I.e., does it contain a status...

From looking at the stack trace I guess there was a `null` refresh token. That might have been caused by the empty responses.

This is an interesting read which explains why these types are needed: https://medium.com/@robert.broeckelmann/understanding-openid-connect-series-37c93d25e92b

Always refreshing the access token if there is a refresh token sounds like a waste of bandwidth. At the very least an implementation should check the expiration date first. There...

Good point. I'll take care of that.

I just checked, the latest version of the httpurlconnection-executor is actually 0.20. I see there is a version [1.16.2](https://mvnrepository.com/artifact/org.dmfs/httpurlconnection-executor/1.16.2) on Maven Central. Not sure how that came into being. Must...

We don't have anything like that in place yet. I'm not even sure there is a practical solution to this. For infinite rules this is apparently impossible unless you start...

I was able to reproduce this issue and I'll look into it. Thanks for reporting.