Fix hostname validation in SCMU #5241
Merged
Conversation
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
# Fix hostname validation in SCMU ## Summary This PR completes the fix for issue #5190 by adding proper hostname validation to ServiceControl.Config. While PR #5238 partially addressed the issue by allowing dashes in hostnames, it didn't implement comprehensive hostname validation, leaving users able to enter invalid hostnames that would cause configuration issues. ## Background **Original Issue**: #5190 reported that ServiceControl.Config was not properly validating hostname fields, allowing users to enter invalid values that would cause runtime failures. **Previous Fix**: PR #5238 addressed part of the problem by allowing dashes in hostnames, but the validation was still incomplete and didn't prevent other invalid hostname formats. **This Fix**: Implements comprehensive RFC-compliant hostname validation using .NET's built-in `Uri.CheckHostName()` method. ## Validation Behavior The new validation accepts: - ✅ Valid DNS hostnames (server01, myhost.domain.com) - ✅ localhost - ✅ Hostnames with dashes (server-01, my-host.domain.com) - *previously fixed by PR #5238*
cquirosj
force-pushed
the
scmu-hostname-validator-bug-fix-5238
branch
from
e9d61c9 to
7db3347
Compare
cquirosj
force-pushed
the
scmu-hostname-validator-bug-fix-5238
branch
from
e836e0a to
8750593
Compare
cquirosj
force-pushed
the
scmu-hostname-validator-bug-fix-5238
branch
from
a6d8d13 to
c886435
Compare
ngallegos
approved these changes
Dec 23, 2025
src/ServiceControl.Config.Tests/Validation/EditAuditInstanceValidationTests.cs
Outdated
Show resolved
Hide resolved
…lidationTests.cs Co-authored-by: Nick Gallegos <nick.gallegos@particular.net>
cquirosj
changed the title
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.
Fix hostname validation in SCMU
Summary
Along with
this PR fixes
This PR completes the fix for issue #5190 by adding proper hostname validation to Service Control Management Utility (SCMU). While PR #5238 partially addressed the issue by allowing dashes in hostnames, it didn't implement comprehensive hostname validation, leaving users able to enter invalid hostnames that would cause configuration issues.
Background
Original Issue: #5190 reported that ServiceControl.Config blocked typing dashes but lacked validation of hostname fields, allowing users to enter invalid values that would cause runtime failures.
Previous Fix: PR #5238 addressed part of the problem by allowing dashes in hostnames, but the validation was still incomplete and didn't prevent other invalid hostname formats.
This Fix: Implements comprehensive RFC-compliant hostname validation using .NET's built-in
Uri.CheckHostName()method.Validation Behavior
The new validation accepts: