From c2e98211782f315efdeaf5f17888781d89e22a77 Mon Sep 17 00:00:00 2001
From: Erik Abele https://example.com:8080/
https://example.com:8080/
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:
+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.