You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
letengineServer=engine.attach(httpsServer);engineServer.on('connection',function(socket: any){debugger;// socket.request.headers does not contain X-TEST headerconsole.log(['connection',socket]);socket.send('test');socket.on('message',function(data: any){console.log(['message',data,socket]);});socket.on('close',function(){console.log(['close',socket]);});});
Expected behaviour
Headers are transferred from browser to client
Setup
OS: Mac OS X Sierra
browser: Google Chrome Version 55.0.2883.95 (64-bit)
engine.io version: 2.0.0
Other information (e.g. stacktraces, related issues, suggestions how to fix)
The problem seems to be little bit further along the road, to be specific with
in xhr.setDisableHeaderCheck(true); xhr doesn't contain setDisableHeaderCheck, so what's the reason to accept extraHeaders if they will be cancelled later?
The text was updated successfully, but these errors were encountered:
You want to:
Current behaviour
The feature #519 doesn't work. ExtraHeaders cancelled out through the call to undefined function in xhr called
setDisableHeaderCheck
.Steps to reproduce (if the current behaviour is a bug)
Browser code:
Server code:
Expected behaviour
Headers are transferred from browser to client
Setup
Other information (e.g. stacktraces, related issues, suggestions how to fix)
The problem seems to be little bit further along the road, to be specific with
engine.io-client/lib/transports/polling-xhr.js
Line 200 in b1baf8d
in
xhr.setDisableHeaderCheck(true);
xhr doesn't contain setDisableHeaderCheck, so what's the reason to accept extraHeaders if they will be cancelled later?The text was updated successfully, but these errors were encountered: