This is actually a great project. Makes it really easy to set up a reverse proxy for test purposes and control it programatically and has a lot of tweakability (adding stuff like latency is trivial). Surely the best of among alternatives for integration testing of .Net applications.Reply
Why do people chose names for tools or libraries starting with "Yet Another...". I know naming can be hard, but anything can be better.
Want a name, here are a few: Camel, Druid, Beetle, Quetzalcoatl, Omaha. You can even use a random website name generator, or character name generator to get names that don't mean anything but are readable.Reply
this is like spring cloud gateway? looks pretty coolReply
when they say reverse proxy server does it mean like nginx? so this tool is like create your own nginx instead of configuring and existing reverse proxy server like nginx?Reply
Any comparisons and/or benchmarks with Traefik or NGINX?Reply
I was interested until I saw .NET and XML on the getting started page.Reply
It is a nice idea (ASP.NET is a great platform), but it is not really ready for broad use.
I gave it a try, because I'm a .NET dev and nginx configuration always confuses me. There are a lot of things still missing from YARP:
- Configuration/API still has some rough edges - For a lot of things (funky header stuff), you still need to write your own Middlewares - Missing documentation for a lot of features - No good Letsencrypt support - Caching and cache conrol is also very limited
I've not examined this in detail, but it'll have to go some to beat Golang's stdlib for easily coding up a reverse proxy.
I've had to do it a few times now for special applications and each time the reverse proxy part was mere minutes of work compared to the application code.Reply
I wonder how this handles TLS. I have tried using dot-net's HttpListener object but was a little disappointed in how it handled TLS.
(In the end, I used HttpListener in localhost-only mode and had an off-the-shelf proxy service to deal with TLS.)Reply
Well good for them for not picking name used by any opensource this time.
An example of inner source becoming open source; YARP began as a way to unify multiple internal .NET reverse proxy projects. Once mature and used internally it was opened up to the rest of the world...Reply
We use Azure AD Application Proxy because it's an approved technology/pattern. Sadly SAML auth doesn't work with MSAL 2.x frontends because auth tokens are clobbered - gh bug #3420 - so we're looking at replacing it.
Right now the USP of Azure AD Application Proxy is that it "just works", give or take a bit of powershell. Replicating the functionality behind their Azure edge network and proxy connector groups is costly. It would be helpful if this project dove-tailed with the Azure edge side so we could run our own proxy connectors.Reply
Recognizing that YARP's goal is to be, well, a reverse proxy, I'm none the less hopefully that a Toolkit-like ecosystem that is currently missing with the stagnacy of Ocelot pops up around YARP.Reply
Great, now dogfood it to the guys responsible for "netsh interface portproxy", easily the most unreliability "OS level" port proxying I've ever seen.Reply
I bet that Hot Fuzz fans greatly approve of the name.Reply