[reSIProcate] handling 401 response to notify

[Elizabeth Clark]

I noticed a subscription is terminated if sending a NOTIFY results in a 401
Unauthorized.
Is there is reason the NOTIFY is not resent using digest credentials if it
has it?
 
The code related to this is in Dialog::dispatch where the msg is a response
and the C_Seq is NOTIFY.  The following if fails because the lastRequest is
null.
 
if ( lastRequest && mDum.mClientAuthManager.get() &&
mDum.mClientAuthManager->handle( *lastRequest, msg ) )
 
In RFC 3265, section 3.2.2 it says "A the NOTIFY is considered failed if ...
a non-200 class response is received ... and no implied further action which
can be taken...".  I believe, however if the agent has the credentials, it
should be able to resend the NOTIFY.
 
Is this a bug?
 
Regards,
Liz


 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050315/9839d8c2/attachment.htm>