[Serdev] FW: [Serusers] limiting expires time
Jamey Hicks
jamey.hicks at hp.com
Mon May 17 15:56:47 UTC 2004
Chris Crawford wrote:
>I will put the enhancement into the registrar module. IMHO it should be
>part of the registrar module and not a core option, so that it could be
>set on a user-by-user basis. For instance, there may be a group (ACLs)
>associated with limiting user registration times (normal users). There
>also may be another group associated with 'permanent' registration times
>(gateways, admins, etc.). It allows more flexibility with each
>registration request.
>
>Below is the functionality that can be expected:
>
>1- If a maximum expires is set, then each contact in the 200 reply that
>has an expires time greater than the max will be set to the maximum
>expires.
>2- If the expires header has a time greater than the configured max,
>then the 200 reply header will be set to the maximum expires.
>
>Is this reasonable? Thoughts?
>
>
It makes sense to me. I implemented this locally for a deployment last
month. Patch attached. The patch also makes the default expires value
a parameter, rather than hardcoding it.
-Jamey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: max-expires.patch
Type: text/x-patch
Size: 2593 bytes
Desc: not available
Url : http://lists.iptel.org/pipermail/serdev/attachments/20040517/cc4fdb19/max-expires.bin
More information about the Serdev
mailing list