httpx 0.24 OAuth1Auth integration broken?

[marban]

Haven't gotten into the details but by upgrading httpx to 0.24 and using
OAuth1Auth from authlib.integrations.httpx_client, I can no longer use e.g. Twitter's API and get an unauthorized header back. Reverting to the previous versions resolves this.

I assume it has to do with their recent change:

• Query parameter encoding switches from using + for spaces and %2F for forward slash, to instead using %20 for spaces and treating forward slash as a safe, unescaped character. This differs from requests, but is in line with browser behavior in Chrome, Safari, and Firefox. Both options are RFC valid. (Use '%20' for encoding spaces in query parameters. encode/httpx#2543)