Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

linux chrome -> tightvncserver on windows 8 fail #8

Open
franck34 opened this issue May 24, 2013 · 0 comments
Open

linux chrome -> tightvncserver on windows 8 fail #8

franck34 opened this issue May 24, 2013 · 0 comments

Comments

@franck34
Copy link

I can connect, but the red box stay is it initial state, nothing append in my browser.

Server side logs:

connec```t request received: 192.168.0.3:5900
socket connected
data arrived:UkZCIDAwMy4wMDgK, length: 16
data arrived:AAAAAtdYyE8grXlqjHY5GulY, length: 24
data arrived:6FU=, length: 4

Client side logs:

connected to 192.168.0.3:5900 VNCClient.js:42
RFBClient: decodedDatalen :12, arrLen: 12 RFB.js:79
RFBClient: Server Version RFB: 003.008 RFB.js:79
RFBClient: Sending Client Version RFB 3.3 RFB.js:79
RFBClient: decodedDatalen :3, arrLen: 3 RFB.js:79
RFBClient: decodedDatalen :15, arrLen: 15 

(no error in the console)

I'm using node 0.10.7 and because you can now use Buffer to convert data, i've patched jstcp with that :

BEFORE

  if(typeof(TCPUtil.base64.decode) === 'function'){
     var base64decoded = TCPUtil.base64.decode(data.data);
     raw = new Buffer(base64decoded, 'binary');
  } else {
    TCPUtil.log("ERROR: NO base64 decoder available.");
  }

AFTER

   raw = new Buffer(data.data, 'base64').toString('binary');
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant