AspNetCore.Proxy
ProxyKit
Our great sponsors
AspNetCore.Proxy | ProxyKit | |
---|---|---|
1 | 3 | |
488 | 1,082 | |
- | - | |
4.1 | 3.1 | |
about 2 months ago | over 3 years ago | |
C# | C# | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
AspNetCore.Proxy
-
Should I call an external API from my Angular client or ASP.NET back-end?
By setting up your backend as a proxy to another API, you're setting up extra code: your front end makes a request to your back end, and your back end makes an almost identical request to another API, which means more code to maintain and more unit tests to write. A lot of the code duplication goes away if you use a package like AspNetCore.Proxy to do most of the heavy lifting with implementing a proxy.
ProxyKit
-
Microsoft YARP
Worth noting that YARP (or as someone has eloquently described it as PRAY) here was another Microsoft project which basically killed a previous open source project which did the same thing:
https://github.com/proxykit/ProxyKit
-
How to migrate PHP Laravel API to ASP.NET Core?
This actually feels like one of the instances that PeachPie with a combination of ProxyKit or YARP would be handy.
-
ASP.NET Core WebApi Authentication with Identity
You could setup a proxy with ProxyKit in you WebHost. Your blazor app will send requests to, say http://webhost:5000/api/endpoint. The host will then forward the request to http://webapi:3000/endpoint (or whatever). You'll have to setup some kind of JWT authentication where the WebHost generates a JWT on login and saves it in the cookie. Good thing here is, the cookie really only contains some id the server uses to look up the actual contents of the cookie. Only the cookie gets returned to the browser (blazor app). On each api request, the webhost will fetch the token out of the server-side cookie and append it to the Authorization header. The webapi will validate the token and return the response that will be proxied back to your front-end.
What are some alternatives?
ASP.NET Boilerplate - ASP.NET Boilerplate - Web Application Framework
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
demo-serverless-aspnetcore - ASP.Net Core 3.1 on AWS Lambda demo
YARP - A toolkit for developing high-performance HTTP reverse proxy applications.
dotnet-microservices-boilerplate - The Ultimate Microservices Starter Kit for .NET Developers!
ABP - Open Source Web Application Framework for ASP.NET Core. Offers an opinionated architecture to build enterprise software solutions with best practices on top of the .NET and the ASP.NET Core platforms. Provides the fundamental infrastructure, production-ready startup templates, application modules, UI themes, tooling, guides and documentation.
C++ REST SDK - The C++ REST SDK is a Microsoft project for cloud-based client-server communication in native code using a modern asynchronous C++ API design. This project aims to help C++ developers connect to and interact with services.
Bitwarden - The core infrastructure backend (API, database, Docker, etc).
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
envoy - Cloud-native high-performance edge/middle/service proxy
nopCommerce - ASP.NET Core eCommerce software. nopCommerce is a free and open-source shopping cart.