[sr-dev] [Tracker] Updated: (SER-50) Expires header in PUBLISH

Expires header in PUBLISH ------------------------- Key: SER-50 URL: http://tracker.iptel.org/browse/SER-50 Project: SER Issue Type: Bug Environment: server: as installed at pals.interne2.edu client: pua.pl v1.29 Reporter: Conny Holzhey Assigned To: Jan Janak Priority: Minor Fix For: 0.9.5 content of Expires header seemingly has no effect. When sending a message like this: PUBLISH sip:xyz@pals.internet2.edu SIP/2.0 Via: SIP/2.0/UDP p549D53FC.dip.t-dialin.net:5060;branch=z9hG4bK18891119775736@p549D53FC.dip.t-dialin.net To: <sip:xyz@pals.internet2.edu> From: <sip:xyz@pals.internet2.edu>;tag=1119775736 Call-ID: 0.388817072221176(a)p549D53FC.dip.t-dialin.net CSeq: 1 PUBLISH Max-Forwards: 70 User-Agent: pua.pl 1.29 Event: presence Expires: 30 Content-Type: application/pidf+xml Content-Length: 227 ... the server returns a message SIP/2.0 200 OK like this: SIP/2.0 200 OK Via: SIP/2.0/UDP p549D53FC.dip.t-dialin.net:5060;branch=z9hG4bK18891119775736@p549D53FC.dip.t-dialin.net;received=84.157.83.252 To: <sip:yivi@pals.internet2.edu>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-957d From: <sip:yivi@pals.internet2.edu>;tag=1119775736 Call-ID: 0.388817072221176(a)p549D53FC.dip.t-dialin.net CSeq: 1 PUBLISH ETag: etag Server: Sip EXpress router (0.10.99.dev7 (i386/linux)) Content-Length: 0 Warning: 392 207.75.164.71:5060 "Noisy feedback tells: pid=17209 req_src_ip=84.157.83.252 req_src_port=26906 in_uri=sip:yivi@pals.internet2.edu out_uri=sip:yivi@pals.internet2.edu via_cnt==1" issues: 1) there shold be a Expires header in the 200 OK message (according to rfc 3903) 2) the server should drop the published information after 30 seconds, but it still reports it after 5 minutes 3) When the client sets the Expires header to 0, it should be removed immediately.