From: Ken Coar Date: Fri, 23 Oct 1998 15:14:14 +0000 (+0000) Subject: Add a 'howto' item submitted in April of 1998 (ouch!). X-Git-Tag: 1.3.4~39 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=775a5f2cf8ff9f458f3b5a4046c13244f1aac3ad;p=thirdparty%2Fapache%2Fhttpd.git Add a 'howto' item submitted in April of 1998 (ouch!). Submitted by: David Sedlock Reviewed by: Ken Coar git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@82307 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/howto.html b/docs/manual/misc/howto.html index 980d4061aa7..df1f45c12eb 100644 --- a/docs/manual/misc/howto.html +++ b/docs/manual/misc/howto.html @@ -24,6 +24,8 @@ How to: URL
  • reset your log files
  • stop/restrict robots +
  • proxy SSL requests through your non-SSL + server
    @@ -161,6 +163,46 @@ in which they can roam, create a robots.txt file; refer to the robot information pages provided by Martijn Koster for the syntax.

    +
    +

    How to proxy SSL requests through + your non-SSL Apache server +
    + (submitted by David Sedlock) +

    +

    +SSL uses port 443 for requests for secure pages. If your browser just +sits there for a long time when you attempt to access a secure page +over your Apache proxy, then the proxy may not be configured to handle +SSL. You need to instruct Apache to listen on port 443 in addition to +any of the ports on which it is already listening: +

    +
    +    Listen 80
    +    Listen 443
    +
    +

    +Then set the security proxy in your browser to 443. That might be it! +

    +

    +If your proxy is sending requests to another proxy, then you may have +to set the directive ProxyRemote differently. Here are my settings: +

    +
    +    ProxyRemote http://nicklas:80/ http://proxy.mayn.franken.de:8080
    +    ProxyRemote http://nicklas:443/ http://proxy.mayn.franken.de:443
    +
    +

    +Requests on port 80 of my proxy nicklas are forwarded to +proxy.mayn.franken.de:8080, while requests on port 443 are +forwarded to proxy.mayn.franken.de:443. +If the remote proxy is not set up to +handle port 443, then the last directive can be left out. SSL requests +will only go over the first proxy. +

    +

    +Note that your Apache does NOT have to be set up to serve secure pages +with SSL. Proxying SSL is a different thing from using it. +