On 03/02/07, Roland Weber <[EMAIL PROTECTED]> wrote:
Hi Sebastian,
in short: because it was designed that way.
The values from the default HostConfiguration will be used if
server-relative (=path-absolute) URIs are fed into HttpClient.
You can either convert the URI to a relative one before feeding
it to HttpClient, or you can modify it to have the protocol
you want to be used.
We can't change HttpClient to not update the protocol, just as
we can't change it to not update the server, if an absolute
URI is given. The values from the URI take precedence, that's
the way it's supposed to be. If you send a request to an https
URL, followed by a request to an http URL, you don't want the
second request to use https just because it happens to be the
second request instead of the first one.
hope that helps,
Roland
Thanks - I understand that one cannot allow the scheme to propagate
from one request to the next. However, I don't understand why the
protocol for that scheme is reset to the default.
I would have thought it was safe to allow the protocol to propagate,
so long as it was for the same scheme?
Sebastian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
