Skip to content

Some issues when using Signalr in cross domain #462

Closed
fantasia949 opened this Issue Jun 19, 2012 · 2 comments

2 participants

@fantasia949

The first issue happend when using long pooling transport in IE9.

In jquery.signalr-0.5.1.js, line 447

  getUrl: function (connection, transport, reconnecting, appendReconnectUrl) {
        /// <summary>Gets thes url for making a GET based connect request</summary>
        var baseUrl = transport === "webSockets" ? "" : connection.baseUrl,
            url = baseUrl + connection.appRelativeUrl,

The point is connection.baseUrl points to origin domain, not the target domain.

The second issue happens when using websocket in all supported browsers

In jquery.signalr-0.5.1.js, line 606:

         protocol = info.protocol === "https:" ? "wss://" : "ws://";

          url = protocol + info.host;

Once more, info.host points to origin domain, not the target domain.

@davidfowl
SignalR member

Why did you close this?

@fantasia949

That issue is duplicated with #461, but I cannot delete it.
Sorry for that inconvenience,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.