xhr-multipart not proxied

[fjakobs]

I'm, trying to use socket.io's xhr-multipart transport but the connection is always closed after the first chunk of data. Looks like there is a problem with transfer encoding chunked.

[Marak]

Could you provide a test case that reproduces this?

[fjakobs]

Sure. This is a very basic test with socket.io. https://gist.github.com/1075579

You need to have socket.io 0.6.x and http-proxy in path. Then open the app in Firefox. If you navigate to the socket.io server at http://localhost:6666 you will see the connect message in the console.

If you navigate to the proxied request at http://localhost:6060 the multipart-xhr connection is opened and immediately closed again.

[dominictarr]

hmm, I am unable to reproduce this. It loads okay. but never logs connect

If I point chrome at localhost:6666

I get Error 312 (net::ERR_UNSAFE_PORT): Unknown error.

okay, i'm reproducing this in firefox with socket.io@0.6.0

Can you make a simpler test that does not require a browser or socket.io?

I know some things socket.io does will not work behind a proxy. (like using multiple ports) prehaps this should be posted as a socket.io issue?

[Marak]

The tests currently use: https://github.com/nodejitsu/node-http-proxy/blob/master/vendor/websocket.js as the websocket client.

[dominictarr]

@Marak in @jakobs script he sets socket.io to use xhr-multipart, so socket.io falls back to that instead of websockets.

https://gist.github.com/1075579#L7

[fjakobs]

I was able to reduce the bug and remove the socket.io dependency https://gist.github.com/1088883.
Note that you have to test this with Firefox because other browsers don't support multipart xhr. I think this exposes some problems with chunked encoding and connection keep-alive.

[dominictarr]

good work.

I can see it work in firefox (note, firebug must be installed - to get console.log)
If you request localhost:6666/xhr (bypass proxy) it works correctly.
If you request localhost:6060/xhr (through proxy) it does not work.

the same behaviour occurs with curl.

I will tag this as confirmed bug, migrate this test to vows, then fix.

thanks @fjakobs, good hunting!

[fjakobs]

Thanks. Good luck fixing

[dominictarr]

I think this might be a bug in core's handling of keep-alive.

I expanded your gist to request to your keep-alive server. by passing the proxy it still doesn't work. it does not get the response body. However, if you comment out headers['Connection'] = 'keep-alive'; it does work.

here is my gist: https://gist.github.com/1113432

there are lots of issues for keep-alive in node: https://github.com/joyent/node/issues/search?q=keep-alive

[subnetmarco]

Any update on this?

[jcrugzz]

Closing due to old age, this should no longer be an issue