Setting response headers (Access-Control-Allow-Origin) about go-socket.io HOT 6 CLOSED

What scenario do you need this header for? I imagine it would be necessary for cross domain XHR polling.

from go-socket.io.

Yep. It's no longer an issue for me though.

from go-socket.io.

Given the complexities and cross-browser differences involved, it probably makes sense to leave this out of go-socketio and go-engineio?

from go-socket.io.

Which complexities do you mean? Headers are set server side, should have nothing to do with browsers? What browsers do with those headers is a different matter, but surely it makes sense to be able to set those headers?

from go-socket.io.

To keep things clean I think it makes more sense to address this with middleware.

from go-socket.io.

You can set the special headers in your ServeHTTP function then call socketio.ServeHTTP. It's not a part of socket.io or engine.io.

I'll close the issue.

from go-socket.io.