Fix expiry based on TTL; fix error handling of dynamodb:DescribeTable

[jackmuskopf]

Addresses this issue:
#86

Also changes error handling for DescribeTable to assume the table does not exist only if the error is ResourceNotFoundException

[jackmuskopf]

In this PR https://github.com/ca98am79/connect-dynamodb/pull/83/files changes everything from ms to seconds, which is correct, since DynamoDB TTL uses epoch time in seconds. However, you can see that sess.cookie.maxAge does not change in this PR, which it should because the Express session cookie maxAge is specified in ms. It needs to be converted to seconds to work with DynamoDB TTL.

I am also running this patch now, let me know if anything needs clarified for fixed. Happy to look at it more.

Thanks,
Jack

[tfrancois]

The PR is actually wrong gents. The update should be this:

? now + sess.cookie.maxAge / 1000 : now + oneDayInSeconds;

[jackmuskopf]

The PR is actually wrong gents. The update should be this:

? now + sess.cookie.maxAge / 1000 : now + oneDayInSeconds;

Isn't that what the PR has? The : now + oneDayInSeconds; is just on the next line (which was not changed)

[ca98am79]

thank you!

[MaxMEllon]

@jackmuskopf @tfrancois @ca98am79

This patch include a issue. Because cookie max-age expected second (is not mill second) by cookie specification.
A cookie expired time become multiply thousandfold If this patch used with cookie.maxAge option.

The Max-Age attribute indicates the maximum lifetime of the cookie, represented as the number of seconds until the cookie expires.
refs : https://httpwg.org/specs/rfc6265.html#max-age-attribute

[MaxMEllon]

I've noticed something.
It seems that express-session sets “cookie.maxAge” in mill seconds while next-session sets “cookie.maxAge” in seconds.
So the problem caused in my application when upgraded [email protected] from [email protected].
However, this may not be a connect-dynamodb problem.

refs: hoangvvo/next-session#369
refs: hoangvvo/next-session#386