Add explicitly-allowed-ports #212
Open
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
When taking screenshots of web services running on non-standard ports, chrome can classify them as 'Unsafe' and throw a net::ERR_UNSAFE_PORT error.
Proposed Solution
To prevent this the
--explicitly-allowed-portflag was implemented in chrome. Unfortunately it appears that each port must be explicit and ranges such as 1-65535 or wildcards are not supported. This creates a comma-separated list from 1-65535 and sets it as the--explicitly-allowed-portflag value, allowing screenshots to be taken on web services running on any port.