Properly handle incorrect port numbers in parseURL (fixes #4200) #4213
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.
This Pull Request fixes issue 4200 (#4200).
Previously, inputs for very large port numbers (more than the 16 bit capacity of the field) was handled incorrectly i.e. lexicalCast returns a zero for such inputs.
The code in this PR returns a boolean value of false if the port number is zero.
This code also handles the case of an input of zero (0) to the port number field.