Fix to use Proxy #324
Merged
Fix to use Proxy #324
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In addition, the following command was executed - npm update - yarn upgrade
DeviaVir
approved these changes
Jun 16, 2017
Collaborator
DeviaVir
left a comment
DeviaVir
left a comment
There was a problem hiding this comment.
I wouldn't accept someone's hardcoded proxy as a PR, but having this configurable is of course great! Thanks!
…-lambda into fix_to_make_proxy_available
Contributor
Author
|
Thank you! |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since it was requested twice(#296, #322), I implemented it.
If you do not need it, please reject it!
reference: http://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/node-configuring-proxies.html
In addition, the following command was executed