diff options
| author | Andy Green <andy@warmcat.com> | 2010-11-08 17:04:09 +0000 |
|---|---|---|
| committer | Andy Green <andy@warmcat.com> | 2010-11-08 17:04:09 +0000 |
| commit | 3c974691f502831537a7428792084ea58cc8cf58 (patch) | |
| tree | 457499f173c75c59218ff6eca04ca24d41176269 /README-test-server | |
| parent | 3faa9c716c4b802e502bdb511c1cd9cdf9abb49f (diff) | |
convert-to-autotools.patch
Signed-off-by: Andy Green <andy@warmcat.com>
Diffstat (limited to 'README-test-server')
| -rw-r--r-- | README-test-server | 20 |
1 files changed, 18 insertions, 2 deletions
diff --git a/README-test-server b/README-test-server index bc9af54..7727ab7 100644 --- a/README-test-server +++ b/README-test-server @@ -1,6 +1,7 @@ Using test-server as a quickstart --------------------------------- +$ ./configure --enable-openssl $ make $ sudo make install $ libwebsockets-test-server @@ -11,12 +12,27 @@ If you point your browser (eg, Chrome) to http://127.0.0.1:7681 -It will fetch "./test-server/test.html", and then run the +It will fetch a script in the form of test.html, and then run the script in there on the browser to open a websocket connection. Incrementing numbers should appear in the browser display. +To test it using SSL/WSS, just run the test server with + +$ libwebsockets-test-server --ssl + +and use the URL + + https://127.0.0.1:7681 + +The connection will be entirely encrypted using some generated +certificates that your browser will not accept, since they are +not signed by any real Certificate Authority. Just accept the +certificates in the browser and the connection will proceed +in first https and then websocket wss, acting exactly the +same. + test-server.c is all that is needed to use libwebsockets for serving both the script html over http and websockets. -2010-10-31 Andy Green <andy@warmcat.com> +2010-11-08 Andy Green <andy@warmcat.com> |