On 12/15/06, frank rittinger <[EMAIL PROTECTED]> wrote:
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag
> >
>
> If you don't want the proxy decrypting the traffic, then you
> don't want an HTTP proxy, you want a port-forwarder. Just
> tell your
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag
> >
>
> If you don't want the proxy decrypting the traffic, then you
> don't want an HTTP proxy, you want a port-forwarder. Just
> tell your OS or firewall to forward port 443 on to the
> back-e
On 12/14/06, frank rittinger <[EMAIL PROTECTED]> wrote:
Thanks for the answer,
As far as I understand it, this would mean that the client talks to my proxy
with one certificate and then the proxy decrypts and encrypts the request and
uses the original servers certificate to communicate with th
certificates.
Cheers, Frank
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag
> von Joshua Slive
> Gesendet: Donnerstag, 14. Dezember 2006 16:01
> An: users@httpd.apache.org
> Betreff: Re: [EMAIL PROTECTED] Problem using apache as a reverse
>
On 12/14/06, frank rittinger <[EMAIL PROTECTED]> wrote:
Hello list,
I'm trying to get apache2 working as a reverse proxy.
Regular HTTP requests just work fine, but I can't get it working for
HTTPS requests.
On startup of apache, I get the following error in the logs:
You configured HTTP(80) on
Hello list,
I'm trying to get apache2 working as a reverse proxy.
Regular HTTP requests just work fine, but I can't get it working for
HTTPS requests.
On startup of apache, I get the following error in the logs:
You configured HTTP(80) on the standard HTTPS(443) port!
Although, I just want to
