maxAge is not being updated, reflects the time the server was started #2
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
…ther is calculated and cached at middleware allocation time
jpallen
added a commit
that referenced
this pull request
Oct 2, 2011
maxAge is not being updated, reflects the time the server was started
|
Thanks a lot, I'll bump the version number and push this fix out soon |
|
I've pushed out version 0.0.2 which includes this fix. Thanks |
|
woohoo, I'll move our project off of my fork and onto 0.0.2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fix issue where cookie maxAge is not updated for each request, but rather is calculated and cached at middleware allocation time