allow using custom client config in checkConnection() method #206
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.
I found the client will throw error of "400 BAD request" when running behind the proxy.
based on this article: https://stackoverflow.com/questions/60578209/axios-proxy-configuration-causing-bad-request
In order to make the client working behind the proxy, I found I need to add some custom parameters in the RPClient,
I found the solution will work in the startLaunch() method, but not checkConnection(), then I need to realize we need to pass the restClientConfig object to checkConnection() as well, after this fix, then we can use the client work under the corporate proxy using the above code snippet.