This repository has been archived by the owner on Mar 27, 2024. It is now read-only.
whoisquery: fix expiration date parsing #575
Merged
Conversation
This file contains 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
ilyam8
changed the title
ilyam8
changed the title
|
This pull request has been mentioned on Netdata Community. There might be relevant details there: https://community.netdata.cloud/t/go-plugin-whois-monitor-cant-get-correct-expiration-time/1304/3 |
vlvkobal
approved these changes
May 17, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes: #574
The fix is using https://github.com/araddon/dateparse for parsing the expiration date. The library allows parsing date strings without knowing the format in advance.