Add option to NewRemoteAllocator to avoid URL detection #990
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.
Summary
This PR solves issue #972.
RemoteAllocatorOption
was added, which containsFetchJSONDebuggerURL
. This could avoid URL detection onNewRemoteAllocator
.PersistDebuggerURL
, an instance ofRemoteAllocatorOption
was added, withFetchJSONDebuggerURL
as false.Example
Consider connecting to a
wss://
URLwill connect to the WebSocket and scrape the page correctly -- it currently does not connect and errs a
HTTP 301