Fixing proxy usage #233
Closed
Fixing proxy usage #233
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
Collaborator
|
@lucarosty Could you please test v5.0.0 and let me know if it fixed your proxy issue? |
Contributor
Author
|
@alex-friedl: I will try today if I found time. But checking the code of version 5.0.0 of this modules and the version 13.6.0 of firebase admin I'm quite sure that the fcm does not use proxy. This is due to 2 different reason
|
Contributor
Author
|
No also the version 5 is not working |
Collaborator
|
@lucarosty Do you think you could provide a fix based on v5? |
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.
This request is a completion of my other request. In the previous request the authorization httpAgent was not set and also to use proxy is needed to fallback to http1.1