dotnet / dotnet/aspnetcore

Issue when YARP is combined into a "normal" app

Open
#44,085 15 comments 0 reactions 0 assignees View on GitHub
area-networking
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe the bug

After moving to .NET7, I found a problem, that occures, when YARP is part of the application.
Since it seems to be somewhere between YARP, ASP.Net core and .NET7, I like to bring it to your attention here.

It makes using NET7 for use-cases with BFF driven by YARP "difficult" and ends up in lots of these:
```
AmbiguousMatchException: The request matched multiple endpoints. Matches:

/Index
/Index
/Index
```

Heres the Issue with repro https://github.com/microsoft/reverse-proxy/issues/1864

### Expected Behavior

I'd expext YARP not to break by upgrading from .NET6 to .NET7

### Steps To Reproduce

https://github.com/glatzert/YARPBug

### Exceptions (if any)

_No response_

### .NET Version

7.0.100-rc.1.22431.12

### Anything else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.