Don't consider "oserror.ErrNotExist" as a failure when trying to erase a session which corresponds to a missing file.
Hello, in the current implementation if a request contains a session token that has been stored in a file that has been deleted the and we're trying to erase it using the Options.MaxAge = -1 workaround, the action still fails, because the missing file error gets propagated higher in the stack.
This small fix prevents this, and ensures that the session is regenerated.
Please let me know if you have any feedback. Having this merged would help tremendously with one of the projects I'm working on.
Summary of Changes
Don't consider "oserror.ErrNotExist" as a failure when trying to erase a session which corresponds to a missing file.
Hello, in the current implementation if a request contains a session token that has been stored in a file that has been deleted the and we're trying to erase it using the
Options.MaxAge = -1
workaround, the action still fails, because the missing file error gets propagated higher in the stack.This small fix prevents this, and ensures that the session is regenerated.
Please let me know if you have any feedback. Having this merged would help tremendously with one of the projects I'm working on.