You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by er...@apache.org on 2008/03/01 18:47:04 UTC
svn commit: r632637 -
/httpd/httpd/branches/2.0.x/docs/manual/ssl/ssl_howto.html.en
Author: erikabele
Date: Sat Mar 1 09:47:04 2008
New Revision: 632637
URL: http://svn.apache.org/viewvc?rev=632637&view=rev
Log:
Transformations.
Modified:
httpd/httpd/branches/2.0.x/docs/manual/ssl/ssl_howto.html.en
Modified: httpd/httpd/branches/2.0.x/docs/manual/ssl/ssl_howto.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.0.x/docs/manual/ssl/ssl_howto.html.en?rev=632637&r1=632636&r2=632637&view=diff
==============================================================================
--- httpd/httpd/branches/2.0.x/docs/manual/ssl/ssl_howto.html.en (original)
+++ httpd/httpd/branches/2.0.x/docs/manual/ssl/ssl_howto.html.en Sat Mar 1 09:47:04 2008
@@ -228,7 +228,7 @@
plain HTTP access for clients on the Intranet?</a></h3>
<p>Let us assume the Intranet can be distinguished through the IP
- network 192.160.1.0/24 and the subarea on the Intranet website has
+ network 192.168.1.0/24 and the subarea on the Intranet website has
the URL <code>/subarea</code>. Then configure the following outside
your HTTPS virtual host (so it applies to both HTTPS and HTTP):</p>