Closed zglozman closed 8 years ago
If you don't force polling the client should automatically upgrade to websockets. What server are you using? I know there was a version of a python based server that didn't properly handle a forced websockets connection.
node.js with the most standard configuration var debug = require('debug')('http') var app = require('http').createServer(handler) var io = require('socket.io')(app); var fs = require('fs'); var Logger = require('socket.io-logger')();
io.use(Logger); function handler (req, res) { res.end('Error loading index.html'); res.writeHead(200); res.end(data); }
app.listen(8108); var tcpProxyServer = require('../src/TcpProxyServer'); // or pass no server and then you can call the method
io.serveClient(false); io.attach(app);
var proxy = new tcpProxyServer(io, "127.0.0.1"); proxy.init();
My guess it's something to do with that proxy server. Have you tried the JS client from a browser?
will try no, but my guess it will work, its something on ios side, maybe no websocket w/o ssl ?
For your pics it doesn't look like it's trying to use HTTPS.
i understand but maybe i should ?
iOS 9 is a lot stricter about connections and TLS, so maybe.
Was this resolved?
And essentially i dont know what i did. the problem is on the swift side.
When using
I get this from which is clearly using polling which is not what i want
or if i use ForceWebsockets it just does this and sever does not get connect event, what can i do ?