Jsclient (v.2.0.2) send null data with SSE when jsonp is enabled

[kocakden]

Hi,

When I use newest javascript client to connect to my server using SSE and jsonp enabled, the data I sent is received null. I tried the same code with version 2.0.1 and I don't get the same error.
Here is my js code

        var url = "http://my.test.local/echo";
        var conn = $.connection(url);
        conn.logging = true;

        conn.error(function (error) {
            console.log('SignalR error: ' + error);
        });
        conn.connectionSlow(function () {
            console.log("We are currently experiencing difficulties with the connection.");
        });
        conn.start({ jsonp: true, transport: ['webSockets', 'serverSentEvents', 'longPolling'] }).done(function () {
            conn.send("data");
        });

if I set the jsonp: false or use the old version (2.0.1), the data is sent correctly.

[DamianEdwards]

We added support for cross-domain SSE in 2.0.2 but appears it might have an issue here. We'll take a look.

[abnanda1]

@kocakden you should not set jsonp to true and everything should work fine. If we need to use jsonp because CORS is not supported, we'll do that in SignalR you don't need to set anything explicitly. We'll consider removing this option in the future versions to avoid any confusion.

[kocakden]

@abnanda1 I stopped using jsonp option and updated my server to set the header values (i.e. Access-Control-Allow-Origin) on response.

[DamianEdwards]

Closing as it appears this was a usage issue.