On Wed, 2008-11-05 at 16:17 +0100, Cech. Ulrich wrote:
> sending 'Proxy-Connection: close' which is wrong given the fact that NTLM
> requires a persistent connection in order to function.>
>
> Hi Oleg,
>
> But how can it be explained, that a non-ssl target is handled correct? The
> wire-log show
Hi Oleg,
But how can it be explained, that a non-ssl target is handled correct? The
wire-log shows a "Proxy-connection: closed" too, but the authentication
works fine.
And if I open the ssl-target over a browser (the same proxy is used), it
worked fine, too.
Perhaps, do I have to set some more h
On Wed, 2008-10-29 at 09:17 +0100, Cech. Ulrich wrote:
> Hi Oleg,
>
> Thanks for your reply.
> Correct, I use the NTLM-support like it is described in the documentation
> (with jcifs etc.). And that worked fine for no-SSL-targets.
>
> Thanks for your help,
> Ulrich
>
>
Ulrich,
The version of
;http://s-hqw2k3bd.pmbelz.de/cgi-bin/chpasswd.cgi";>change your
default password.[\r][\n]"
[DEBUG] wire - << "[\r][\n]"
[DEBUG] wire - << "[\n]"
[DEBUG] wire - << "[\n]"
[DEBUG] wire - << "[\n]"
[DEBUG] wire - << &quo
On Mon, 2008-10-27 at 15:46 +0100, Cech. Ulrich wrote:
> Hello,
>
> I have a problem with SSL target over a proxy. I use the example of the
> HttpClient-code (4.0 beta), without an SSL-target, everything work fine.
> But if I change the target to port 443 and https (s. commented line), I
> receive
Hello,
I have a problem with SSL target over a proxy. I use the example of the
HttpClient-code (4.0 beta), without an SSL-target, everything work fine.
But if I change the target to port 443 and https (s. commented line), I
receive the "HTTP/1.0 407 Proxy Authentication Required" from the proxy (a
