0

I’m migrating a web form project to a dotnet core project (with a react front end) using a strangler fig approach.

I’m able to get successful routing to my webforms app. However,the client side routing stopped working in the react app.

If I enter a route that exists in the react project, it seems as if precedence is given to the YARP proxy and a get request is sent to my web forms project.

Is there anyway I can give precedence to React routing. If it doesn’t exist in the React project then use the proxy to check the webforms project?

If it’s an issue with React we are also willing to try Blazor. Or would we have to forgo SPA solutions, when using a reverse proxy? Also in the reverse proxy I am using catch-all. Can this cause an issue?

0 Answers0