David Muller

Thanks for the report @ulf5. > The elasticsearch lib handles this by itself, but it would be nice for other services. Yes, as you've observed we previously removed query string...

Thanks for getting back I could see the convenience of putting the optional quoting in this package, I agree. That said, at this time I would probably not accept a...

> Can you guys suggest me the changes I should make to have this s3 compatible Hi @pghole - this library has turned out to be relatively limited - it...

Not planning on merging this one as the [use case seems to involve non AWS services](https://github.com/DavidMuller/aws-requests-auth/issues/38#issuecomment-416975582).

Hi @avoidik -- can you describe your use case? See also previous PRs (e.g. https://github.com/DavidMuller/aws-requests-auth/pull/11) that have adjusted what is ultimately placed in the `SignedHeaders` portion of the `Authorization` header.

I do not have plans for a new release soon - my company has stopped using this package. In the meantime, a workaround is to use the `get_aws_request_headers_handler` hook exposed...

Hi @f0rk - thanks for the pull request. `aws-requests-auth`'s intended target is `requests` - since `httpx` is still in beta and not technically `requests` compatible, I do not think this...

Thanks for the update @timofurrer -- I'll follow along with the discussion in PR #157

I think the crux of this boils down to the fact that there's no way to encode `[]` in multipart? ``` python from rest_framework.test import APIClient client = APIClient() client._encode_data({'foo':[1,...