Client handshake returns error message "Transport unknown" #1577

Maxwell2022 · 2014-06-02T05:16:17Z

I was trying to initialize a handshake, following the specs I've found at LearnBoost/socket.io-spec. Sometime I found that it has to be done with a POST request, sometime with GET. I've tried both of them and they both returned the same error:

GET http://acme.local:3700/socket.io/1
or
POST http://acme.local:3700/socket.io/1

{
"code": 0,
"message": "Transport unknown"
}

The text was updated successfully, but these errors were encountered:

RB-Develop · 2014-06-04T09:07:12Z

This is a problem for me as well. I can't run benchmarks for testing the Socket.io performance on my server due to this error.

I see this is not a local error seeing that the demo chat application on the Socket.io homepage has the same issue. http://chat.socket.io/socket.io/1 returns the exact same response.

Maxwell2022 · 2014-06-04T09:14:35Z

It's due to the version of socket.io. I had to downgrade to v0.9.x because I could not find any documentation about the way to perform handshake with version v1.0.x

alexiskattan · 2014-06-04T09:45:02Z

+1

gregtap · 2014-06-06T00:15:13Z

Make sur that the client and server libs are 1.0.x

Maxwell2022 · 2014-06-06T01:56:04Z

I'm not using the javascript client but a custom PHP client. So it needs to handle the handshake. I'll wait to get some documentation about it or might have a look, if I have time, how the javascript client is actually performing the handshake.

ghost · 2014-06-11T08:39:47Z

+1

i'm debugging with fiddler

chat.socket.io not using 'chat.socket.io/socket.io/1'

gmmateev · 2014-06-11T14:35:40Z

I experience the same issue when I manually send the handshake request.

piascikj · 2014-06-13T16:09:21Z

Some more documentation on how to accomplish a handshake with 1.0.x would be very helpful. I'm receiving the same error. I can't find any of the query params on the server side that I applied using

var socket = io("http://localhost:8080", {query:{bla:"bla"});

or

var socket = io("http://localhost:8080", {query:"bla=bla"});

francoisTemasys · 2014-06-17T03:43:44Z

Same problem here using a C++ library.
Doing a POST request to the server like this:

Send Handshake Post request...:
POST /socket.io/1/ HTTP/1.1
Accept: */*
Content-Type: text/plain
Host: localhost
Connection: Keep-Alive

It returns:

[ERRFMT] Bad Request
response: {"code":0,"message":"Transport unknown"}

What have changed?

ghost · 2014-06-17T05:30:10Z

no documents in this update!

francoisTemasys · 2014-06-17T06:29:00Z

I don't know if that would help:
When requesting:

GET /socket.io/1/?EIO=2&transport=polling HTTP/1.1
Accept: */*
Content-Type: text/plain
Host: localhost
Connection: Keep-Alive

On 0.9.4:

response: 9svmBRkeQuECcpw6ZGPK:60:60:websocket,htmlfile,xhr-polling,jsonp-polling

On 1.0.4:

response:   �0{"sid":"ySaqnVO4pJajP_TfAAAM","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":60000}

ghost · 2014-06-17T07:12:01Z

@francoisTemasys

i testing with chat example source.

first. get sid

Send: Return Code: 0x00000000
GET /socket.io/?EIO=2&transport=polling&t=1402968982931-0 HTTP/1.1
Accept: */*
Referer: http://localhost:3000/
Accept-Language: ko-KR
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Host: localhost:3000
DNT: 1
Connection: Keep-Alive

second. request same url with sid, again, handshake is done

Send: Return Code: 0x00000000
GET /socket.io/?EIO=2&transport=polling&t=1402968982946-1&sid=UwY0AcBHl84hz1FvAAAb HTTP/1.1
Accept: */*
Referer: http://localhost:3000/
Accept-Language: ko-KR
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Host: localhost:3000
DNT: 1
Connection: Keep-Alive
Cookie: io=UwY0AcBHl84hz1FvAAAb

third. connect to websocket, but i can't succeed.. socket.io not responses heartbeat.

Send: Return Code: 0x00000000
GET /socket.io/?EIO=2&transport=websocket&sid=UwY0AcBHl84hz1FvAAAb HTTP/1.1
Origin: http://localhost:3000
Sec-WebSocket-Key: t1eDysQI92E+9v3n0mq6sA==
Connection: Upgrade
Upgrade: Websocket
Sec-WebSocket-Version: 13
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Host: localhost:3000
DNT: 1
Cache-Control: no-cache
Cookie: io=UwY0AcBHl84hz1FvAAAb

francoisTemasys · 2014-06-17T07:30:33Z

I tried here is the output on 1.0.4:

First GET:

GET /socket.io/1/?EIO=2&transport=polling HTTP/1.1
Accept: */*
Content-Type: text/plain
Host: localhost
Connection: Keep-Alive

RESPONSE:
[ERRFMT] OK
response:   �0{"sid":"AmcxWuqqPAFapV74AAAC","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":60000}

Second Query with the sid:

GET /socket.io/1/?EIO=2&transport=polling&sid=AmcxWuqqPAFapV74AAAC HTTP/1.1
Accept: */*
Content-Type: text/plain
Host: localhost
Connection: Keep-Alive

RESPONSE:
[ERRFMT] OK
response: ��40

haih · 2014-07-10T08:54:44Z

same error

adantart · 2014-07-10T18:26:37Z

same error here !

nenadvulic · 2014-07-18T12:25:32Z

same for me

yvan01 · 2014-07-23T16:27:06Z

Hey, this might help, you can set the response to return plain text by setting b64=true in the request. (you also need to set the transport in the request)

For example:
https://localhost:3030/socket.io/?EIO=2&transport=polling&t=1406120775060-0&b64=true

This returns (content-type:text/plain)
97:0{"sid":"g75H5D6feFrj9cCDAAAB","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":60000}

Also, the packet returned seems to have the following format:

In the above example
Message length = 97
Type = 0 (Open)
Data = {"sid":"g75H5D6feFrj9cCDAAAB","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":60000}

Hope it helps, but you should know I'm new to socket.io so there may be other adjustments you need to make that I'm not aware of.

hemstar7 · 2014-07-25T15:18:08Z

same error here !

crawft · 2014-08-05T15:42:23Z

+1 :(

maggialejandro · 2014-08-12T15:16:38Z

Same here, I'm using socket.io v1.0.6 on both client and server..
I find out that the browser-sync ~0.8.2 (uses socket.io 0.8.7) was causing the problem, BrowserSync/browser-sync#71

akkunchoi · 2014-10-06T06:38:08Z

I've encountered same error on socket.io v1.1.0.

I added a follow line at server side script, then I fixed this problem.
io.set('transports', ["websocket", "polling"]);

Errors I encountered:

GET /socket.io returns Transport unknown.
DEBUG=* node-dev app.js prints a lot of unknown transport polling.

I refer http://stackoverflow.com/questions/23962047/socket-io-v1-0-x-unknown-transport-polling

rase- · 2014-10-06T10:10:59Z

We'll definitely work on adding more documentation about the handshake to socket.io-protocol, where I feel like this issue belongs.

rase- · 2014-10-06T10:19:28Z

Closing this in favor of socketio/socket.io-protocol#10.

If this issue occurs when using socket.io (not a custom implementation) what @coulix said is likely the fix: make sure that the client and server are of the same version. Please do open another issue about it if this doesn't help. :)

Kernelzero · 2015-09-14T08:33:50Z

same error

steviesama · 2015-09-26T19:33:04Z

I actually got through the first 2 completing the handshake, and the on connection emit actually fires and I pick it up in the serial monitor of my Arduino, but the third connection upgrade request I get bad request. So frustrating.

Narasimha-Murthy · 2016-03-25T12:34:13Z

when i try open socket my getting error message is
2016-03-25 17:47:36.043 szx[3499:103945] ERROR: handshake failed ... The request timed out.

altanai · 2016-05-02T13:44:18Z

since im also facing this , i guess its not fixed uptill now . im using "socket.io": "^1.4.5",

rosarionakkocom · 2016-05-24T21:27:23Z

For Those still looking for an answer for here:

https://www.npmjs.com/package/passport.socketio

kevinguard · 2016-08-05T08:52:49Z

@rosarionakkocom That didn't help.

drekka · 2017-02-03T04:12:10Z

Just hit this as well. Trying various options. Am just lying to test out a server I've built and using PAW as a client.

afshinm · 2017-05-19T18:40:53Z

I fixed this problem by adding this setting to my socket.io server:

var socket = io({
  transports: [
    'websocket', 
    'flashsocket', 
    'htmlfile', 
    'xhr-polling', 
    'jsonp-polling', 
    'polling'
  ]
});

read more here: http://stackoverflow.com/a/24244413/375966

darrachequesne · 2017-05-22T20:17:05Z

@afshinm please note that, as documented there, the order in transports options is important:

Note: The order is important. By default, a long-polling connection is established first, and then upgraded to WebSocket if possible. Using ['websocket'] means there will be no fallback if a WebSocket connection cannot be opened.

pathbox · 2018-03-03T03:11:51Z

@afshinm Thanks, it works

darrachequesne · 2018-03-09T12:33:58Z

Please note that since socket.io version 1.x, the only valid values for transports are:

websocket
polling

All the other values in @afshinm 's answer won't be used (in fact, only websocket transport will be used in that case).

AngelliaX · 2021-04-02T04:09:58Z

Closing this in favor of socketio/socket.io-protocol#10.

If this issue occurs when using socket.io (not a custom implementation) what @coulix said is likely the fix: make sure that the client and server are of the same version. Please do open another issue about it if this doesn't help. :)

it works !!!, my client side is using a lib call elephant.io, and it is using verison of 1.0.0, but my socket.io is using 4.0.0, so i install the socket version 1.0.6 (as i see in the terminal) and the problem is fixed even though i dont know why

rase- mentioned this issue Oct 6, 2014

Document the handshake process socketio/socket.io-protocol#10

Closed

rase- closed this as completed Oct 6, 2014

uncvrd mentioned this issue Feb 28, 2019

Determining nginx upstream values for websocket sticky sessions caprover/caprover#379

Closed

Client handshake returns error message "Transport unknown" #1577

Client handshake returns error message "Transport unknown" #1577

Comments

Maxwell2022 commented Jun 2, 2014

RB-Develop commented Jun 4, 2014

Maxwell2022 commented Jun 4, 2014

alexiskattan commented Jun 4, 2014

gregtap commented Jun 6, 2014

Maxwell2022 commented Jun 6, 2014

ghost commented Jun 11, 2014

gmmateev commented Jun 11, 2014

piascikj commented Jun 13, 2014

francoisTemasys commented Jun 17, 2014

ghost commented Jun 17, 2014

francoisTemasys commented Jun 17, 2014

ghost commented Jun 17, 2014

francoisTemasys commented Jun 17, 2014

haih commented Jul 10, 2014

adantart commented Jul 10, 2014

nenadvulic commented Jul 18, 2014

yvan01 commented Jul 23, 2014

hemstar7 commented Jul 25, 2014

crawft commented Aug 5, 2014

maggialejandro commented Aug 12, 2014

akkunchoi commented Oct 6, 2014

rase- commented Oct 6, 2014

rase- commented Oct 6, 2014

Kernelzero commented Sep 14, 2015

steviesama commented Sep 26, 2015

Narasimha-Murthy commented Mar 25, 2016

altanai commented May 2, 2016

rosarionakkocom commented May 24, 2016

kevinguard commented Aug 5, 2016

drekka commented Feb 3, 2017

afshinm commented May 19, 2017

darrachequesne commented May 22, 2017

pathbox commented Mar 3, 2018

darrachequesne commented Mar 9, 2018

AngelliaX commented Apr 2, 2021