Hi,
We're trying to implement registration with
digest authorization.
The specification for the authorization is in
RFC 2617 (HTTP Authentication: Basic and Digest
Access Authentication).
The section regarding calculation of A2 says:
3.2.2.3 A2
If the "qop" directive's value is "auth" or is unspecified, then A2
is:
A2 = Method ":" digest-uri-value
If the "qop" value is "auth-int", then A2 is:
A2 = Method ":" digest-uri-value ":" H(entity-body)
I believe that I am right in saying that the H(x) function
is simply the MD5 (RFC1321) hashing function. But what
does "entity-body" refer to?
RFC 2616 (Hypertext Transfer Protocol -- HTTP/1.1) says:
7.2 Entity Body
The entity-body (if any) sent with an HTTP request or response is in
a format and encoding defined by the entity-header fields.
entity-body = *OCTET
An entity-body is only present in a message when a message-body is
present, as described in section 4.3. The entity-body is obtained
from the message-body by decoding any Transfer-Encoding that might
have been applied to ensure safe and proper transfer of the message.
Unfortunately, this means nothing to me.
Can anyone tell me what "entity-body" refers to in SIP?
Thanks,
Attila Sipos
Software Engineer
DDI ( +44 1344 784918 )
<mailto:[EMAIL PROTECTED]>
<http://www.vegastream.com>
____________________________________________________________________________
_______
VegaStream : A World of difference for your Integrated Communications
EMEA Office (UK)
Tel + 44-1344 784900 Fax + 44-1344 784901
USA Office
Tel + 1-415-954-8528 Fax + 1-415-954-8598
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
