You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Providing a custom endpoint and a tls: false configuration options to clients still result in "https" protocol to be used in the fetch-http-handler.
This is causing issues while setting localhost server as mock servers for S3 since local mock server is only running on http protocol. Related issue: aws-amplify/amplify-js#5320
SDK version number
Beta.3
Is the issue in the browser/Node.js?
Browser
To Reproduce (observed behavior)
Pass the following configuration options to any client and check the request made in the network tab has https protocol
Expected behavior
http-handler (fetch or a custom provided one) should use the right http protocol based on tls flag or from the endpoint value (aws-sdk V2).
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.
lockbot
locked as resolved and limited conversation to collaborators
May 5, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Providing a custom
endpoint
and atls: false
configuration options to clients still result in "https" protocol to be used in the fetch-http-handler.This is causing issues while setting localhost server as mock servers for S3 since local mock server is only running on http protocol. Related issue: aws-amplify/amplify-js#5320
SDK version number
Beta.3
Is the issue in the browser/Node.js?
Browser
To Reproduce (observed behavior)
Pass the following configuration options to any client and check the request made in the network tab has https protocol
Expected behavior
http-handler (fetch or a custom provided one) should use the right http protocol based on tls flag or from the endpoint value (aws-sdk V2).
The text was updated successfully, but these errors were encountered: