StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POCross domain requests not working in SignalR 2.0.0-rc1
primarykey
Id
18471853
data
AcceptedAnswerId
18473005
AnswerCount
4
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-27T17:25:15.030
FavoriteCount
3
LastActivityDate
2016-05-13T10:51:52.047
LastEditDate
LastEditorUserId
0
OwnerUserId
506236
ParentId
0
PostTypeId
1
Score
6
ViewCount
12807
LastEditorDisplayName
text
Body
I recently upgraded a project from SignalR 2.0.0-beta1 to 2.0.0-rc1. I understand that in RC1, configuration of support for cross domain requests changed. I've updated my project to use the new syntax however I'm now getting the following error when attempting to communicate with my hub: <blockquote> XMLHttpRequest cannot load =1377623738064">http://localhost:8080/negotiate?connectionData=%5B%7B%22name%22%3A%22chathub%22%7D%5D&clientProtocol=1.3&=1377623738064. Origin <code>http://localhost:7176</code> is not allowed by Access-Control-Allow-Origin. </blockquote> The client site is running at <code>http://localhost:7176</code> and the hub is listening via a console application at <code>http://localhost:8080</code>. Am I missing something here? Cross domain requests were working before I upgraded to RC1. CONSOLE APP ENTRY POINT <pre><code>static void Main(string[] args) { var chatServer = new ChatServer(); string endpoint = "http://localhost:8080"; chatServer.Start(endpoint); Console.WriteLine("Chat server listening at {0}...", endpoint); Console.ReadLine(); } </code></pre> CHATSERVER CLASS <pre><code>public class ChatServer { public IDisposable Start(string url) { return WebApp.Start<Startup>(url); } } </code></pre> STARTUP CONFIGURATION <pre><code>public class Startup { public void Configuration(IAppBuilder app) { app.Map("/signalr", map => { map.UseCors(CorsOptions.AllowAll); map.RunSignalR(new HubConfiguration { EnableJSONP = true }); }); } } </code></pre>
Tags
<c#><signalr><cors>
Title
Cross domain requests not working in SignalR 2.0.0-rc1
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USScott
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POCross domain requests not working in SignalR 2.0.0-rc1
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POCross domain requests not working in SignalR 2.0.0-rc1
 UserUserId
 USShulhi Sapli
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.