diff options
author | Pierre Ossman <ossman@cendio.se> | 2017-02-03 16:02:17 +0100 |
---|---|---|
committer | Pierre Ossman <ossman@cendio.se> | 2017-02-03 16:09:08 +0100 |
commit | 10e13d7a7e679360a2cb2bc22cd2b0d964c5acb6 (patch) | |
tree | 1271f05883873a4f07699671ec86a39d481bce23 /docs | |
parent | e47591f4aaa0221a187d3ea2f61c7ab5bb93ed54 (diff) | |
download | websockify-10e13d7a7e679360a2cb2bc22cd2b0d964c5acb6.tar.gz |
Remove last bits of Flash WebSocket emulation
We require native support from the browsers now.
Diffstat (limited to 'docs')
-rw-r--r-- | docs/notes | 18 | ||||
-rw-r--r-- | docs/websockify.1 | 5 |
2 files changed, 1 insertions, 22 deletions
@@ -1,21 +1,3 @@ -Some implementation notes: - -There is an included flash object (web-socket-js) that is used to -emulate websocket support on browsers without websocket support -(currently only Chrome has WebSocket support). - -Javascript doesn't have a bytearray type, so what you get out of -a WebSocket object is just Javascript strings. Javascript has UTF-16 -unicode strings and anything sent through the WebSocket gets converted -to UTF-8 and vice-versa. So, one additional (and necessary) function -of wsproxy is base64 encoding/decoding what is sent to/from the -browser. - -Building web-socket-js emulator: - - cd include/web-socket-js/flash-src - mxmlc -static-link-runtime-shared-libraries WebSocketMain.as - Building release tarball: - not really necessary since tagged revision can be downloaded from github as tarballs diff --git a/docs/websockify.1 b/docs/websockify.1 index ab04b7a..c4b97b7 100644 --- a/docs/websockify.1 +++ b/docs/websockify.1 @@ -65,13 +65,10 @@ Daemonizing: When the -D option is specified, websockify runs in the background SSL (the wss:// WebSockets URI): This is detected automatically by websockify by sniffing the first byte sent from the client and then wrapping the socket if the data starts with '\\x16' or '\\x80' (indicating SSL). .IP * -Flash security policy: websockify detects flash security policy requests (again by sniffing the first packet) and answers with an appropriate flash security policy response (and then closes the port). This means no separate flash security policy server is needed for supporting the flash WebSockets fallback emulator. - -.IP * Session recording: This feature that allows recording of the traffic sent and received from the client to a file using the --record option. .IP * -Mini-webserver: websockify can detect and respond to normal web requests on the same port as the WebSockets proxy and Flash security policy. This functionality is activate with the --web DIR option where DIR is the root of the web directory to serve. +Mini-webserver: websockify can detect and respond to normal web requests on the same port as the WebSockets proxy. This functionality is activate with the --web DIR option where DIR is the root of the web directory to serve. .IP * Wrap a program: see the "Wrap a Program" section below. |