>Hi Nirmalya, > >1. yes, the "entity-body" is the SIP message body. Not exactly. There is a subtle difference. Qouting from RFC 2617: "H(entity-body) is the hash of the entity body, not the message body - it is computed before any transfer encoding is applied by the sender and after it has been removed by the recipient. Note that this includes multipart boundaries and embedded headers in each part of any multipart content-type." >2. yes, the method is the SIP method. > >Regards, > >Attila > > >Attila Sipos >Software Engineer > ><http://www.vegastream.com> > >VegaStream : A World of difference for your Integrated Communications > ___________________________________________________________________________ _ >______ > > >> -----Original Message----- >> From: Nirmalya Ghosh [mailto:[EMAIL PROTECTED]] >> Sent: 11 January 2002 15:32 >> To: [EMAIL PROTECTED] >> Subject: [Sip-implementors] Doubts regarding "request-digest" >> calculation in Authorization request header >> >> >> Hi All, >> >> I have a few doubts regarding the calculation of "request-digest" for >> the "response" directive of the Authorization request header >> (Defined in >> Section 3.2.2 of RFC-2617). Both my doubts originate from >> Section 3.2.2.3 of the same document. >> [1] Firstly, the "entity-body" in the case of SIP messages >> is the same >> as the message body, right? >> [2] Secondly, I am assuming that the "Method" value would >> be the SIP >> Methods and not HTTP, am I correct in assuming so? >> >> Thanks & Regards, >> Nirmalya >> >> _______________________________________________ >> Sip-implementors mailing list >> [EMAIL PROTECTED] >> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors >> _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
