Skip to content
This repository has been archived by the owner on Oct 10, 2018. It is now read-only.

Should websockets work on release versions of ASP.NET Core and .NET Core? #66

Closed
starquake opened this issue Aug 17, 2017 · 2 comments
Closed

Comments

@starquake
Copy link

starquake commented Aug 17, 2017

This is more of a support request than an issue maybe. If this is the wrong place for this question please direct me somewhere else.

When I run the samples it forwards websockets to an Angular Cli running ng serve just fine. When I try to use it with my newly created ASP.NET Core 2.0 that I created with VS 2017 15.3 it doesn't work. The forwarding works perfectly but it has trouble upgrading the connection to websockets.

I have the UseWebSockets in place:

            app.UseWebSockets().RunProxy(new ProxyOptions
            {
                Scheme = scheme,
                Host = host,
                Port = port
            });

And it proxies the HTTP stuff just fine, so I think I'm close.

Is there more documentation about how to use this?

Here's the result of the request:
image

@starquake
Copy link
Author

To answer my own question: It seems only to be working in the v2.1.0 preview. If this is by design, feel free to close.

@aspnet-hello
Copy link

This issue was moved to aspnet/Home#2492

@aspnet aspnet locked and limited conversation to collaborators Jan 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants