Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.8.0-b1
    • Component/s: None
    • Labels:
      None

      Description

      It would be useful to have a validation service that checks whether a hostname is valid. Currently, there are multiple places in modules, and in the core, that perform similar/identical hostname validation checks. See https://www.blesta.com/forums/index.php?/topic/11833-validatehostname-should-accept-uppercase-characters/

      I'm thinking a new utility under /core/Util/Validate/Server that provides a method to validate a server's hostname. Perhaps another to validate an IP address.

      The Zend framework supports a Hostname validator that appears to handle domain/IDN/IP validation but it's apart of a larger library that requires php 5.6+ and adds up to almost 2MB of files. It may be best in the interim to use php's filter_var with FILTER_VALIDATE_DOMAIN and FILTER_VALIDATE_IP.

        Issue Links

          Activity

          Hide
          admin Paul Phillips added a comment -

          Depending on complexity, an initial fix for uppercase characters could be made per https://dev.blesta.com/browse/CORE-2832 While it would be good to have a consistent way of validating hostnames which modules can utilize, this shouldn't slow down a fix for resolving uppercase character validation in individually affected modules.

          Show
          admin Paul Phillips added a comment - Depending on complexity, an initial fix for uppercase characters could be made per https://dev.blesta.com/browse/CORE-2832 While it would be good to have a consistent way of validating hostnames which modules can utilize, this shouldn't slow down a fix for resolving uppercase character validation in individually affected modules.

            People

            • Assignee:
              Unassigned
              Reporter:
              tyson Tyson Phillips (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                23/Dec/19

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 hours, 32 minutes
                4h 32m

                  Agile