Honour ignoreOutsideDomain when set on its own in HostURLFilter - #2074
Merged
Conversation
rzo1
force-pushed
the
fix/hosturlfilter-domain-config
branch
from
August 27, 2026 12:50
47f3163 to
30135b0
Compare
dpol1
approved these changes
Aug 28, 2026
dpol1
left a comment
Member
There was a problem hiding this comment.
LGTM. One thing for the description: only ignoreOutsideHost: false on its own NPE'd, true never reached the domain branch. Worth being precise, since this and the "only ignoreOutsideDomain now restricts" sentence will end up in the 4.0 release notes.
HostURLFilter.configure() read the ignoreOutsideDomain parameter but tested the ignoreOutsideHost node for null. A configuration naming only ignoreOutsideDomain was therefore discarded and the filter let every URL through, while one naming only ignoreOutsideHost: false failed with a NullPointerException while the topology was starting. ignoreOutsideHost: true was never affected, as it short-circuits before the domain parameter is read. Now each parameter is tested independently. Topologies which set only ignoreOutsideDomain: true start restricting the crawl to the source domain, as configured.
rzo1
force-pushed
the
fix/hosturlfilter-domain-config
branch
from
August 28, 2026 07:38
30135b0 to
c1fea7a
Compare
Contributor
Author
|
Both made precise: the NPE is now attributed to |
jnioche
approved these changes
Aug 28, 2026
Contributor
|
thanks @rzo1 |
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
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.
HostURLFilter.configure()read theignoreOutsideDomainparameter but tested theignoreOutsideHostnode for null. A configuration naming onlyignoreOutsideDomainwas silently discarded and the filter let every URL through; one naming onlyignoreOutsideHost: falsethrew aNullPointerExceptionat topology startup.ignoreOutsideHost: truewas never affected, as it short-circuits before the domain parameter is read. Each parameter is now tested on its own.Topologies setting only
ignoreOutsideDomain: truewill start restricting outlinks to the source domain, as configured. Configurations setting both keys, including all three archetypes, are unaffected.For all changes
Is there a issue associated with this PR? Is it referenced in the commit message? - no issue
Does your PR title start with
#XXXXwhereXXXXis the issue number you are trying to resolve? - no issueHas your PR been rebased against the latest commit within the target branch (typically main)?
Is your initial contribution a single, squashed commit?
Is the code properly formatted with
mvn git-code-format:format-code -Dgcf.globPattern="**/*" -Dskip.format.code=false?For code changes
mvn clean verify? -coremodule tests only (348 run, all green)HostURLFilterTest, both fail without the fix