From: Erik Abele Date: Wed, 13 Feb 2008 13:18:16 +0000 (+0000) Subject: Whitespace fixes. X-Git-Tag: 2.3.0~977 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c2e98211782f315efdeaf5f17888781d89e22a77;p=apache Whitespace fixes. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@627396 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/ssl/ssl_faq.xml b/docs/manual/ssl/ssl_faq.xml index 7a861faab5..64d18891d3 100644 --- a/docs/manual/ssl/ssl_faq.xml +++ b/docs/manual/ssl/ssl_faq.xml @@ -175,7 +175,7 @@ relative hyperlinks? is where any HTTPS compliant browser will look by default. You can force your browser to look on a different port by specifying it in the URL. For example, if your server is set up to serve pages over HTTPS on port 8080, - you can access them at https://example.com:8080/

+ you can access them at https://example.com:8080/

How do I speak HTTPS manually for testing purposes? @@ -191,16 +191,16 @@ relative hyperlinks? $ openssl s_client -connect localhost:443 -state -debug
GET / HTTP/1.0
- -

Before the actual HTTP response you will receive detailed - information about the SSL handshake. For a more general command - line client which directly understands both HTTP and HTTPS, can - perform GET and POST operations, can use a proxy, supports byte - ranges, etc. you should have a look at the nifty - cURL tool. Using this, you can - check that Apache is responding correctly to requests via HTTP and HTTPS as - follows:

- + +

Before the actual HTTP response you will receive detailed + information about the SSL handshake. For a more general command + line client which directly understands both HTTP and HTTPS, can + perform GET and POST operations, can use a proxy, supports byte + ranges, etc. you should have a look at the nifty + cURL tool. Using this, you can + check that Apache is responding correctly to requests via HTTP and + HTTPS as follows:

+ $ curl http://localhost/
$ curl https://localhost/
@@ -214,7 +214,7 @@ relative hyperlinks? connect via HTTPS to a HTTP server (eg, using https://example.com/ on a server which doesn't support HTTPS, or which supports it on a non-standard port). Make sure that you're - connecting to a (virtual) server that supports SSL.

+ connecting to a (virtual) server that supports SSL.

Why do I get ``Connection Refused'' messages, when trying to access my newly installed Apache+mod_ssl server via HTTPS?