[3.0] Strip FQDN period from the end of the domain - #230
Open
WyriHaximus wants to merge 1 commit into
Open
Conversation
WyriHaximus
force-pushed
the
3.x-strip-fqdn-period-suffix
branch
5 times, most recently
from
July 9, 2025 08:27
7da7faa to
debe592
比较
WyriHaximus
force-pushed
the
3.x-strip-fqdn-period-suffix
branch
from
July 25, 2025 05:58
debe592 to
1d2007f
比较
As brought up in reactphp#229 we're already treating all domains as absolute, so adding direct support for it is a small bug fix. That said, fully support for search domains requires a different handling of this and will be done in a different PR.
WyriHaximus
force-pushed
the
3.x-strip-fqdn-period-suffix
branch
from
July 25, 2025 06:00
1d2007f to
564bdaf
比较
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
注册 for free
to join this conversation on GitHub.
Already have an account?
登录 to comment
1 participant
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.
As brought up in #229 we're already treating all domains as absolute, so adding direct support for it is a small bug fix. That said, fully support for search domains requires a different handling of this and will be done in a different PR.