Sending logout events
is at rambler-co.ru
Wed Aug 27 17:55:11 MSD 2008
On Wed, Aug 27, 2008 at 10:59:16AM +0200, 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.
This is IMAP/POP3, but not HTTP, there are no cookies.
More information about the nginx