Return-Path:
Delivered-To: apmail-httpd-cvs-archive@httpd.apache.org
Received: (qmail 36835 invoked by uid 500); 23 Dec 2002 16:43:04 -0000
Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
list-help:
list-unsubscribe:
list-post:
Delivered-To: mailing list cvs@httpd.apache.org
Received: (qmail 36822 invoked by uid 500); 23 Dec 2002 16:43:04 -0000
Delivered-To: apmail-httpd-2.0-cvs@apache.org
Date: 23 Dec 2002 16:43:03 -0000
Message-ID: <20021223164303.43404.qmail@icarus.apache.org>
From: erikabele@apache.org
To: httpd-2.0-cvs@apache.org
Subject: cvs commit: httpd-2.0/docs/manual/ssl ssl_faq.xml ssl_faq.html.en
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
erikabele 2002/12/23 08:43:03
Modified: docs/manual/ssl ssl_faq.xml ssl_faq.html.en
Log:
Fixed link to cURL (PR15616).
Revision Changes Path
1.7 +1 -1 httpd-2.0/docs/manual/ssl/ssl_faq.xml
Index: ssl_faq.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_faq.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- ssl_faq.xml 8 Dec 2002 21:05:57 -0000 1.6
+++ ssl_faq.xml 23 Dec 2002 16:43:03 -0000 1.7
@@ -251,7 +251,7 @@
SSL handshake. For a more general command line client which directly
understands both the HTTP and HTTPS scheme, can perform GET and POST
methods, can use a proxy, supports byte ranges, etc. you should have a
- look at nifty cURL
+ look at nifty cURL
tool. With it you can directly check if your Apache is running fine on
Port 80 and 443 as following:
1.9 +1 -1 httpd-2.0/docs/manual/ssl/ssl_faq.html.en
Index: ssl_faq.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_faq.html.en,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- ssl_faq.html.en 11 Dec 2002 21:33:39 -0000 1.8
+++ ssl_faq.html.en 23 Dec 2002 16:43:03 -0000 1.9
@@ -258,7 +258,7 @@
SSL handshake. For a more general command line client which directly
understands both the HTTP and HTTPS scheme, can perform GET and POST
methods, can use a proxy, supports byte ranges, etc. you should have a
- look at nifty cURL
+ look at nifty cURL
tool. With it you can directly check if your Apache is running fine on
Port 80 and 443 as following: