Remote guides - resovle config ’*’ to default whitelist #860
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
oskarhane
force-pushed
the
play-from-guides
branch
5 times, most recently
from
c69e86d
to
b654691
Compare
oskarhane
force-pushed
the
play-from-guides
branch
3 times, most recently
from
e233b67
to
918a9c3
Compare
myzero1
pushed a commit
to myzero1/neo4j-browser
that referenced
this pull request
May 17, 2019
Remote guides - resovle config ’*’ to default whitelist
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.
With the
browser.remote_content_hostname_whitelistconfig set to*, neo4j browser now tries to resolve guides on the default hosts (guides.neo4j.com, localhost) so they more easily can be played.Example:
:play reconow looks for a guide on (in that order)The behavior for configurations of
browser.remote_content_hostname_whitelistset to anything else should be unchanged.Before
After