[GH-ISSUE #30] Sending sometimes logs the user out #27

New issue

Closed

opened 2026-02-25 21:33:57 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 21:33:57 +03:00

Owner

Originally created by @jasonmunro on GitHub (Mar 7, 2016).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/30

Originally assigned to: @jasonmunro on GitHub.

This appears to be a race condition between submitting a message to be sent and background requests, but I'm unsure why it logs the user out. The outbound message is sent, which is even weirder. I have disabled the send button while the background draft saving occurs which helps, but there is still something fishy going on here.

Originally created by @jasonmunro on GitHub (Mar 7, 2016). Original GitHub issue: https://github.com/cypht-org/cypht/issues/30 Originally assigned to: @jasonmunro on GitHub. This appears to be a race condition between submitting a message to be sent and background requests, but I'm unsure why it logs the user out. The outbound message is sent, which is even weirder. I have disabled the send button while the background draft saving occurs which helps, but there is still something fishy going on here.

kerem

2026-02-25 21:33:57 +03:00

closed this issue
added the
bug

smtp
labels

kerem commented

2026-02-25 21:33:57 +03:00

Author

Owner

@jasonmunro commented on GitHub (Mar 8, 2016):

I believe I have tracked this down to a race condition WRT PHP sessions. If I rapidly click on links in the folder list I can trigger a logout. Still hunting down the reason for that. Switching to DB sessions fixes the issue (and is non-blocking so better with parallel requests)

@jasonmunro commented on GitHub (Mar 8, 2016): I believe I have tracked this down to a race condition WRT PHP sessions. If I rapidly click on links in the folder list I can trigger a logout. Still hunting down the reason for that. Switching to DB sessions fixes the issue (and is non-blocking so better with parallel requests)

kerem commented

2026-02-25 21:33:57 +03:00

Author

Owner

@jasonmunro commented on GitHub (Mar 8, 2016):

The problem is session regenerate id. With that disabled I'm unable to reproduce the forced logout bug

@jasonmunro commented on GitHub (Mar 8, 2016): The problem is session regenerate id. With that disabled I'm unable to reproduce the forced logout bug

kerem commented

2026-02-25 21:33:57 +03:00

Author

Owner

@jasonmunro commented on GitHub (Mar 8, 2016):

Removed the session regenerate id call for now. Might try to do something with it later

@jasonmunro commented on GitHub (Mar 8, 2016): Removed the session regenerate id call for now. Might try to do something with it later