Sending logout events
bra at fsn.hu
Thu Aug 28 15:19:22 MSD 2008
On 2008.08.27. 10:59, Grzegorz Nosek wrote:
> On śro, sie 27, 2008 at 10:39:01 +0200, Attila Nagy wrote:
>> Would it be possible to extend this protocol:
>> 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
>> 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.
More information about the nginx