< Previous by Date	Date Index	Next by Date >
< Previous in Thread	Thread Index	Next in Thread >

Re: [reSIProcate] Why is outbound proxy an URI?

From: "Dale R. Worley" <dworley@xxxxxxxxxxx>
Date: Tue, 18 Apr 2006 00:08:53 -0400

On Mon, 2006-04-17 at 22:24 +0200, Matthias Moetje - TERASENS GmbH
wrote:
> I'm just wondering why setOutboundProxy has an URI as 
> parameter.

I suspect that is because it is effectively the value in a Route header.
Letting you specify any URI allows you to arrange for any of the RFC
3263 mechanisms for routing to your proxy.

Dale

References:
- [reSIProcate] Why is outbound proxy an URI?
  - From: Matthias Moetje - TERASENS GmbH

Prev by Date: [reSIProcate] HashMap for g++ > 3
Next by Date: [reSIProcate] Problem with extension headers
Previous by thread: [reSIProcate] Why is outbound proxy an URI?
Next by thread: RE: [reSIProcate] Why is outbound proxy an URI?
Index(es):
- Date
- Thread