6 messages in ru.sysoev.nginxRe: Sending logout events
FromSent OnAttachments
Attila NagyAug 27, 2008 1:38 am 
Grzegorz NosekAug 27, 2008 1:58 am 
Igor SysoevAug 27, 2008 6:54 am 
Grzegorz NosekAug 27, 2008 7:06 am 
Maxim DouninAug 27, 2008 10:44 am 
Attila NagyAug 28, 2008 4:18 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Sending logout eventsActions...
From:Attila Nagy (bra-@public.gmane.org)
Date:Aug 28, 2008 4:18:59 am
List:ru.sysoev.nginx

On 2008.08.27. 10:59, Grzegorz Nosek wrote:

On śro, sie 27, 2008 at 10:39:01 +0200, Attila Nagy wrote:

Hello,

Would it be possible to extend this protocol: http://wiki.codemongers.com/NginxImapCoreModule

with logout (connection closed, timeout, etc) events?

Something like this:

GET /close HTTP/1.0 Host: auth.server.hostname Close-User: user Close-Server: 192.168.1.10 Close-Port: 143 Close-Protocol: imap Close-Cause: logout|server_timeout|client_ssl_timeout|client_closed|server_closed|etc Client-IP: 192.168.1.1

The main benefit would be that the authenticator application could build a session table from live sessions, which is currently very hard to do. This means after an authentication OK response is sent, nginx should send a close event, no matter how the connection was lost (setting the Close-Cause accordingly).

How would you distinguish between multiple sessions from the same client? I guess you'd need a cookie set by the authenticator and sent by nginx when the session ends.

There are internal (or not so internal, because they can be logged) identifiers which could be used as a session ID, but valid point, it should be sent too.