Hi, There is no reason that proxy should keep Proxy-Authorization if that belongs to it (whose realm matches). Some implementations does so. RFC 3261 (sec 22.3) mentioned that -- "When multiple proxies are used in a chain, a Proxy-Authorization header field value MUST NOT be consumed by any proxy whose realm does not match the realm parameter specified in that value."
So proxies may consume Proxy-Authorization header belonging to them. Thanks, Mahipati Deshpande --- "Dale R. Worley" <[EMAIL PROTECTED]> wrote: > On Wed, 2005-12-07 at 11:06 +0000, Mahipati > Deshpande wrote: > > At this point proxy A validates credentials and > > consumes Proxy-Authorization header. If this > request > > spiralled and comes back to proxy A, whether proxy > > challenges again (because there is no > > Proxy-Authorization header ) or it processes as if > it > > passed authentication? > > There is no reason for the proxy to "consume" the > Proxy-Authorization > header. It should *examine* it, but it should leave > it in the request > as it forwards it. (I believe that it is *required* > to leave it in the > request.) That way, if the request spirals, the > proxy will pass it the > second time without further ado. > > Dale > > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > Mahipati Deshpande __________________________________________________________ Yahoo! India Matrimony: Find your partner now. Go to http://yahoo.shaadi.com _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
