I have had trouble connecting Internet Explorer in the newest build of Windows.Net Server (build 3628) to the VNC java applet port 5800 on a system running VNC. I've tried http://{vncserver}:5800 but my browser keeps acting like the VNC server isn't available.
Here is a message from another person in the Windows.Net beta program that shows what the problem is. Can this be put on the fix list for the next build of VNC? Yes, I can see it. Didn't happen in 3621 > > I looked at it in netmon and it appears that VNC server sends \n\n at the end of the standard HTTP > 200 Ok response: > HTTP/1.0 200 OK\n\n > > IIS sends > HTTP/1.0 200 OK\r\n\r\n > > RFC1945 describing HTTP protocol requires using CRLF and not just LF. Apparently IE has been > modified towards stricter protocol compliance. The bug appears to be in VNC, and not in IE. > Fortunately, VNC is available as source code and simply changing line 37 in vncHTTPConnect.cpp from > const char HTTP_MSG_OK [] ="HTTP/1.0 200 OK\n\n"; > > to > > const char HTTP_MSG_OK [] ="HTTP/1.0 200 OK\r\n\r\n"; > > solves the problem. The rest of the messages should be modified too. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
