Dear Rossen,
Thanx for these clear words. From an older thread, which I found
in the archives, I thought the scheme
web client -->HTTPS--> proxy (apache) -->HTTPS--> httpd internal
should work WITHOUT ssl enabled on the proxy, because http,ftp and
connect are just passed by the proxy without additional things to do and
the https is in first instance just a connect request.
So, it seems, I did understand something wrong.
I will now try to solve my problem enabling ssl. But this lets the
task unsolved how I could convince our firewall admin to
enable ssl on his proxy to allow us to offer a secure connection, but
this is not your problem ;-)
Thanx for all the help and your patience,
Oli
[EMAIL PROTECTED] wrote:
> Hi,
>
> Regarding my experience it is impossible to run HTTPS server (including
> proxy server) without SSL support.
> The problem is that you server is receiving not http request but HTTPS
> request.
> To work with this you have to run SSL enabled HTTPD. There is no need you
> internal HTTPD to be SSL enabled.
>
> If the scheme is:
>
> web client -->HTTPS--> proxy (apache) -->HTTP--> httpd internal
>
> then you proxy server have to be SSL enabled. There is no need for you
> internal one.
>
> If the scheme is:
>
> web client -->HTTPS--> proxy (apache) -->HTTPS--> httpd internal
>
> then both your servers have to be SSL enabled.
>
> If the scheme is:
>
> web client -->HTTP--> proxy (apache) -->HTTPS--> httpd internal
>
> Then only you internal server have to be SSL enabled, but I do not see
> reason to one to use scheme like the last one (to protect yourself from
> his local network, but not from the Internet ;)
>
> Rossen
>
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
