Wrong middleware behaviour, when ApiExplorer (ApiVersioning) is integrated. #221

New Issue

fergalmoran · 2025-08-09T17:15:27Z

fergalmoran commented

2025-08-09 17:15:27 +00:00

Originally created by @merqlove on 1/21/2018

So, subj.

Problem:
Wrong behavior means, that existing routes (From MVC Razor stack) redirecting/proxy to the React app.

Also posted here:
https://github.com/Microsoft/aspnet-api-versioning/issues/238

For me this behavior looks WRONG!

Sample project, that illustrates this behaviour:
Sample

I really surprised, that no one has reported this bug.

*Originally created by @merqlove on 1/21/2018* So, subj. Problem: Wrong behavior means, that existing routes (From MVC Razor stack) redirecting/proxy to the React app. Also posted here: https://github.com/Microsoft/aspnet-api-versioning/issues/238 For me this behavior looks WRONG! Sample project, that illustrates this behaviour: [Sample](https://github.com/Mubicon/aspnet-spa-bug) I really surprised, that no one has reported this bug.

fergalmoran closed this issue

2025-08-09 17:15:27 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#221