-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support aws-sdk-kotlin / smithy-kotlin's OkHttp4Engine
#17
Comments
OkHttp4Engine
Hello @lauzadis , Thanks for reaching out! We actually made a change recently that modifies the API to to return the client configuration instead of a client, which should allow your customer to create their own client and then just use our authentication SDK to provide the proper cognito configuration for the client. I can reply directly on that linked issue, and I'll keep this issue open until that one is resolved. |
@cgalvan , If you want to reproduce by yourself.
|
@cgalvan , |
Hello, I am from the AWS SDK for Kotlin team. We have a customer trying to use this project and running into issues with their OkHttp configuration.
We offer an OkHttp4 engine for users that can't rely on the default engine which uses OkHttp5, an alpha version. The customer configured their project to use this
OkHttp4Engine
, but your project creates its own Kotlin SDK clients which still use OkHttp5, causing conflicts for the customer.Are you able to provide some configuration options for users who want to use the OkHttp4Engine? One way this could be done is by accepting a custom Kotlin SDK as an optional parameter wherever it's used. Another option is to configure your own Kotlin SDK clients to use the OkHttp4Engine, since I noticed this project uses OkHttp 4.12.0.
The text was updated successfully, but these errors were encountered: