Thank you, Dale. I was very clear about it.
In summary and confirming, in general, 407 is used by a proxy, but a UA can also use 407. Is it correct? By the way, you said below: > > In general, there is no effective way for a UAC to determine which > element generated a 401/407 response (or any other response), other than > optional UAS identification fields (like Server and Contact) that the > responder chooses to include in the response. > When a UA(SENDER) received 407 from a proxy of itself, why can a UA(SENDER) find out a element(proxy) generated 407? Thanks, Tabt 2010/2/9 Dale Worley <[email protected]>: > On Mon, 2010-02-08 at 18:32 +0900, Couret Tabt wrote: >> I have a question about '407 Proxy Authenticate Response' >> in RFC3261 below: >> >> May a UA(ex.Bob as a receiver) send '407 Proxy Authenticdate' Response >> as same as a proxy send. > > In theory, a UAS must use 401 and a proxy must use 407. But a UAS can > behave as if there is a proxy between itself and the rest of the > network, and that proxy could send a 407. So in practice, a UAS can > send a 407 if it wishes to. > > In general, there is no effective way for a UAC to determine which > element generated a 401/407 response (or any other response), other than > optional UAS identification fields (like Server and Contact) that the > responder chooses to include in the response. > > Dale > > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
