You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other users see the usage of the api hard as well. See the other issues: "How would i write... " (#82) or "I Cant figure what i need write" (#90)
In my case, i wanted to proxy my frontend to a react dev server running localhost:3000, which also includes a websocket connection on wss:localhost:3000/ws (for hot reload etc). I still have no clue how to configure both of it in this library.
The text was updated successfully, but these errors were encountered:
However, and this is important, this library is generally meant for complex scenarios where something like nginx would not fit your needs. For example, it is really designed for scenarios where you want to use the power of C# to do complex proxying. For example, maybe you need to query a database, or a cache, to discover which endpoint the request should be proxied to, or maybe you need to query a complex load-balancing engine to determine the most efficient backend for the request, or maybe (as was my use case many years ago) you are building an SLA-based scheduler that chooses the best endpoint based on the machine most likely to fulfill some intensive compute request within a specified SLA without wasting resources.
Anyway, all that to say, if this library doesn't fit your needs because it is designed for making complex scenarios easier, you are welcome (and encouraged) to use a more ready-made solution like nginx.
well it may be in your case, but not in mine.
Other users see the usage of the api hard as well. See the other issues: "How would i write... " (#82) or "I Cant figure what i need write" (#90)
In my case, i wanted to proxy my frontend to a react dev server running localhost:3000, which also includes a websocket connection on wss:localhost:3000/ws (for hot reload etc). I still have no clue how to configure both of it in this library.
The text was updated successfully, but these errors were encountered: