Sam, The architecture of HttpClient 2.0 is, let me say, well..., sub-optimal. The problem being that in HttpClient 2.0 redirects are handled by HttpMethodBase class, whereas connections are managed by HttpClient (through a HttpConnectionManager to be exact). As a result HttpMethodBase class has no means of obtaining a new connection when cross-sire redirect is requested. For various reasons (mainly due to the popular pressure from other projects reliant on HttpClient 2.0 API) the problem could not be solved for the 2.0 release.
The bug is already fixed in CVS HEAD, but the code may still be unstable. 2.1 release will be free from this limitation. Cheers Oleg On Wed, 2003-11-05 at 20:05, Sam Berlin wrote: > Hi All, > > I'm curious why HttpClient is unable to redirect from one port to > another port. Does the HTTP spec disallow this, or does the internals > of HttpClient break if the redirect occurs? > > Thanks, > Sam > > > --------------------------------------------------------------------- > 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]
