Re: [reSIProcate] DUM Auth

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

Yes – or you could implement onReadyToSend for the various usages.

 

From: Roee Vulkan [mailto:vulkanr@xxxxxxxxx]
Sent: Tuesday, January 09, 2007 12:24 PM
To: Scott Godin; resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [reSIProcate] DUM Auth

 

 

Just a thought - will I be able to do it by assigning an output message decorator that will simply add the relevant header?

 

----- Original Message -----

From: Scott Godin

To: Roee Vulkan ; resiprocate-devel@xxxxxxxxxxxxxxxxxxxx

Sent: Tuesday, January 09, 2007 6:10 PM

Subject: RE: [reSIProcate] DUM Auth

 

Transactions should only go through the authorization process if they are the first client transaction of a dialogset.  All requests within the same dialogset should contain the proxy auth header from the first challenge.    There is currently no way to get dum to include the auth headers on all new client requests.

 

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Roee Vulkan
Sent: Tuesday, January 09, 2007 10:15 AM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] DUM Auth

 

 

Hello.

 

After successfuly being authenticated with the proxy, Is there a way to make DUM use the same "Proxy-Authorization" string on subsequent calls?

 

Currently every transaction is going through the whole authentication process.

 

Thanks.

-Roee.