Re: [reSIProcate] dum ClientPublication end() method: illegal body?
I agree. The RFC is pretty clear on that. Table 1 also indicates that a refresh shouldn't have a body either. Section 4.3 - "A publication refresh only extends the expiration time of already
existing event state. It does not affect that event state in any
other way. Therefore, a PUBLISH request that refreshes event state
MUST NOT have a body."
We should probably fix that at the same time.
Scott
On Sat, Jan 22, 2011 at 11:38 PM, Kennard White
<kennard_white@xxxxxxxxxxxx> wrote:
Hi,
I noticed that resip/dum/ClientPublication's end() method sends a PUBLISH method with Expire: 0 and *with* a PIDF body. In RFC3903, Table 1 and also in section 4.5, it says that a "remove" PUBLISH method "MUST NOT" have a body. Would it make sense to remove the body in this end() method before sending the message? I think this is a simple change, just looking for feedback on correct behavior.
Regards,
Kennard
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel