From: Erik Abele Date: Mon, 23 Dec 2002 16:43:03 +0000 (+0000) Subject: Fixed link to cURL (PR15616). X-Git-Tag: pre_ajp_proxy~2360 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8409da4ab8f91d1e1258a5dc3140ff5f7589fe30;p=apache Fixed link to cURL (PR15616). git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@98096 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/ssl/ssl_faq.html.en b/docs/manual/ssl/ssl_faq.html.en index 01c02921e9..1275ddd32d 100644 --- a/docs/manual/ssl/ssl_faq.html.en +++ b/docs/manual/ssl/ssl_faq.html.en @@ -258,7 +258,7 @@ configuration directive? 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:

diff --git a/docs/manual/ssl/ssl_faq.xml b/docs/manual/ssl/ssl_faq.xml index 82cc410c3c..070e1436e7 100644 --- a/docs/manual/ssl/ssl_faq.xml +++ b/docs/manual/ssl/ssl_faq.xml @@ -251,7 +251,7 @@ configuration directive? 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: