DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24012.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On 23/10/03 2:29 PM, Thamm, Russell [EMAIL PROTECTED]
wrote:
Hi,
I am interested in using NTLM for authentication on my Apache based webdav
server.
I am using the Slide client (based on httpclient)
I understand that HttpClient supports NTLM but requires me to supply the user
Hello Russell,
the functionality to retrieve the logon credentials from the
operating system is very specific to Windows. On Linux,
some projects (Samba client?) implement an extra PAM
(Pluggable Authentication Module) to mimic this behavio.
It's not good style for the OS itself to remember
Hello,
We're trying to connect to an OC4J server through HTTPS. We already got it
working on HTTP, but it seems the client 'forgets' the session state when we
connect to the same server in HTTPS. The first request goes fine, but after
that it seems the state is lost.
The method we use to
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24012.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Was there any significant overhead in using the 1.1 counterparts?
I did not do any performance measurements. Anyways, running on JVM 1.1 one can expect
quite a bit of a performance degradation compared to newer JVMs.
Vector and Hashtable are both synchronized which might be a performance
Sam,
Is the source for the existing 1.1 port available anywhere?
I passed the source onto David (David.Cowan at apcc.com). For my project I had to add
a few features specific to our particular requirements, which rendered it incompatible
with HttpClient 2.0. Unfortunately I no longer have
Hello, I need to use httpclient rc2 to communiate with a untrusted server (self sign).
The server also requires the client to send a client certificate.
Handling untrusted connection over https is straight forward
according to the example in EasySSLProtocolSocketFactory.
The question here is
We've been examining the headers, but the server doesn't seem to send any
cookies (in http it does, but not in https). I was assuming this was
supposed to be done through some under-water process (I'm not very familiar
with https), but the HttpState object does not contain any cookies in its
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24081.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I'm trying to start using the HttpClient (I've always been instantiating
my own HttpConnections and Methods). I want to manually set a cookie to
be sent in the HttpRequest I am making, I can build the cookie myself,
setting the proper domain information. But its unclear to me what the
proper
Hi Mark,
You will want to add the cookies to the HttpClient's HttpState. Please
take a look at the following for an example:
http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/src/
examples/CookieDemoApp.java?rev=1.12content-type=text/vnd.viewcvs-
markup
Oleg has also recently
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15435.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
13 matches
Mail list logo
