This repository has been archived by the owner on May 21, 2022. It is now read-only.
cut-off timestamp after second part (10th digit) #298
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.
as
time.Now().Unix()
returns timestamp with 10 digits,which records to second unit, we need to cut smaller than
second unit (milisecond, nanosecond) to compare timestamps
with integer comparison.
before this PR, integer comparison with
iat, exp, nbf
andnow
can make a correct result under assumption that
iat, exp, nbf
is 10-digits timestamp (which smallest unit is second).
if
iat, exp, nbf
has more digits,now
is always smaller thanthese timestamps, and so always make incorrect verify results.
so i added simple function
func cutOff
which cuts timestampto have first 10-digits only, to satisfy that assumption.