DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27589.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
I have read the notes on the bug in Httpclient V2.0 to do with
using Basic Authentication with a HTTPS Url through a proxy.
One workaround proposed is to use preemptive authentication.
Are the credentials i.e. username, password sent unencrypted to the
target server when Preemptive
+1
On Mar 24, 2004, at 2:24 AM, Adrian Sutton wrote:
Hi all,
Continuing to push this forward, I propose that we adopt the proposal
below
as our formal proposal to the Jakarta PMC to promote HttpClient to a
Jakarta
level project.
Please vote as follows:
Hi Oleg,
Sorry, I completely forgot about this one. Could you send the patch
again, or add it to a bug?
Mike
On Mar 24, 2004, at 5:55 AM, Kalnichevski, Oleg wrote:
Any objections to committing this patch?
Oleg
-Original Message-
From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=25529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=25529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
John,
HttpClient will not/cannot attempt to authenticate with the target server until the
transport layer (SSL tunnel) is up and running. It does not matter if pre-emptive
authentication is used or not, SSL takes care of the transport security between the
client and the target server. Only
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=25529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Michael Becke [EMAIL PROTECTED] wrote on 25/03/2004 12:23:46 AM:
Please vote as follows:
-
Vote: Promote HttpClient to Jakarta level
[X] +1 I am in favor of the proposal, and will help support it.
[ ] +0 I am in favor
Hello Gil,
two options. If you only need to get the cookie for
your application, then access the header directly
instead of looking into the http state. That's probably
what your old code did, right?
Otherwise, implement and configure your own cookie
policy. Copy the default implementation that
Thanks, yes, the old code pulled it out of the header directly, but the
rest of the story is that I save that cookie for later submittal in a
url request. I tried using addRequestHeader(Cookie, ...) and that
didn't work. I surmised that it was because httpclient liked to operate
with higher-level
Ah yes, cookie headers that were manually set used
to get overridden. As far as I remember, that changed
a while back. Though I cannot tell whether the change
went into 2.0 or only into the development branch.
cheers,
Roland
Alvarez, Gil [EMAIL PROTECTED]
25.03.2004 08:04
Please respond
12 matches
Mail list logo