On Mon, 2007-01-29 at 16:52 +0100, Roland Weber wrote: > Hi Oleg, > > > SchemeRegistry maybe? > > Yes, that's better. > > > I think scheme ID is still needed, if we want to be able to support > > custom scheme aliases. Aliased schemes can be very handy when dealing > > with different SSL contexts, for instance. > > > > myhttps1 (some custom SSL settings) -> https > > myhttps2 (some other custom SSL settings) -> https > > Where would the Scheme ID (or rather name) come into play?
Roland, It is necessary when sending requests through a non-transparent proxy, where a full request URI is required. Oleg > Is there some URL transformation logic in HttpClient 3 that > would change myhttps1:// into https:// after the scheme (or > Protocol in 3.x) is looked up? Then I'll have to find a place > for that, too. > > If we find it necessary, I'll add a > > void registerAlias(String alias, Scheme schm) > > to the SchemeRegistry class. That would give us a good place > for explanatory JavaDocs. > > cheers, > Roland > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
