This repository was archived by the owner on May 16, 2018. It is now read-only.
Use relative filenames for _validIdns for direct include in Zend_Validate_Hostname #426
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.
Zend_Validate_Hostname::isValid runs a direct include to add to regex fragments on line 1220.
The first two occurrences of this mechanism in the protected variable $_validIdns on lines 824 and 831 have relative paths to the appropriate files (Hostname/Biz.php and Hostname/Cn.php). Subsequent references from line 832 onwards use a full path (Zend/Validate/Hostname/Com.php).
For those using their own autoloader this is problematic.
This pull request changes all the includes to be consistent and use the relative location. Given the nature of the include this should work for all setups.