We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provided a .org domain with the following response (from rawdata) with dates in Y-m-dTH:i:sZ format:
Y-m-dTH:i:sZ
Updated Date: 2019-09-16T15:39:04Z Creation Date: 2012-10-01T15:32:42Z Registry Expiry Date: 2020-10-01T15:32:42Z
The parsed information in regrinfo has incorrect dates when Y-m-d could theoretically also be Y-d-m. (e.g. 10-01)
regrinfo
changed: 2019-09-16 created: 2012-01-10 expires: 2020-01-10
Created and expires should be 10-01, changed is fine.
Does not seem to happen exclusively on .org domains.
Somewhat related to #38
Using jsmitty12/phpwhois#5.5.0.
jsmitty12/phpwhois#5.5.0
$whoisTarget = 'proper-full-domain.tld'; $whois = new Whois(); $result = $whois->lookup($whoisTarget);
The text was updated successfully, but these errors were encountered:
example domain exhibiting this problem: scottishrecoveryconsortium.org
Sorry, something went wrong.
Merge pull request #54 from jsmitty12/issue_49_incorrect_date_parsing
e9c42f5
Improve parsing of dates in standard format Fixes #49
Successfully merging a pull request may close this issue.
Provided a .org domain with the following response (from rawdata) with dates in
Y-m-dTH:i:sZ
format:The parsed information in
regrinfo
has incorrect dates when Y-m-d could theoretically also be Y-d-m. (e.g. 10-01)Created and expires should be 10-01, changed is fine.
Does not seem to happen exclusively on .org domains.
Somewhat related to #38
Using
jsmitty12/phpwhois#5.5.0
.The text was updated successfully, but these errors were encountered: