Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in
Toggle navigation
N
noVNC
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
rasky
noVNC
Commits
d63e1462
Commit
d63e1462
authored
Apr 07, 2010
by
Joel Martin
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
List for proxy reasons.
parent
5aeb9880
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
9 deletions
+9
-9
README.md
README.md
+9
-9
No files found.
README.md
View file @
d63e1462
...
...
@@ -18,12 +18,12 @@ Requirements
*
Until VNC server support web sockets, you need to use a Web Sockets to
normal socket proxy. There are a couple reasons for this:
*
Web Sockets is not a pure socket protocol. There is an initial HTTP
1.
Web Sockets is not a pure socket protocol. There is an initial HTTP
like handshake to allow easy hand-off by web servers and allow some
origin policy exchange. Also, each Web Sockets frame begins with
0 ('
\x
00') and ends with 255 ('
\x
ff').
*
Javascript itself does not have the ability to handle pure byte
2.
Javascript itself does not have the ability to handle pure byte
strings (Unicode encoding messes with it) even though you can read
them with Web Sockets. The python proxy base64 encodes the data so
that the Javascript client can base64 decode the data into an array.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment