Refering to section 22.1 of rfc3261: For BYE, you should recalculate the
authorization header since the method is changed.
IMO a CANCEL doesn't have to contain a authorization header since it
cannot be challenged. A CANCEL should be accepted by a server if it comes
from the same hop that sent the request being cancelled.
Martin van den Berg.
"Szilagyi, Mike" <[EMAIL PROTECTED]>
Sent by:
[EMAIL PROTECTED]
2005-01-20 05:36 PM
To: <[email protected]>
cc: (bcc: Martin van den Berg/HVS/BE/PHILIPS)
Subject: [Sip-implementors] Question about
Authorization/Proxy-Authorizationfor BYE
and CANCEL
Classification:
With Digest authentication, should the "response" in an Authorization or
Proxy-Authorization header in a BYE request and CANCEL request be the
same as the "response" in the original INVITE that started the session?
Or should it be recalculated since the method type has changed?
I've seen devices use the same response and I've seen other devices
recalculate. Which is correct?
Thanks.
_______________________________________________
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
