RestEase
IdentityModel.AspNetCore
RestEase | IdentityModel.AspNetCore | |
---|---|---|
11 | 2 | |
1,044 | 288 | |
- | - | |
4.6 | 7.4 | |
5 months ago | almost 2 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.
RestEase
-
Best way to implement base class for API calls?
If Swagger/OpenAPI is available, save yourself a lot of trouble and generate the client using OpenAPI Generator. If not, use a library like RestEase to make it significantly easier to create the client.
-
ASP.NET Core - how to properly make a GET request?
Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.
-
RestSharp and gZip compression
Not sure about RestSharp, but with RestEase this is handled by setting it on an HttpClientHandler - https://github.com/canton7/RestEase/discussions/195
-
What do u use in .net 7 for your Client calls in terms of web apis
Use RestEase to make a client.
-
Is it a best practice to use NSwag generated code for calls to a local web API?
I haven't tried this myself, but to take it a step further from just sharing request types you could try using RestEase.
- Aos mais experientes, como fazem para aprender uma nova linguagem/tecnologia?
-
Creating and Using HTTP Client SDKs in .NET 6
Honorable mentions: RestEase, RESTFulSense
-
What do you use to call http endpoints?
I use RestEase which is heavily inspired by Refit.
-
API url strings throughout UI
Take a look at RestEase: https://github.com/canton7/RestEase
- RestEase – Easy-to-use typesafe REST API client library
IdentityModel.AspNetCore
-
Refresh Authentication Token on retry when using Polly
Move your AuthorizationMessageHandler to execute before your resilience policies. You can take inspiration from IdentityServer's implementation: ClientAccessTokenHandler.cs
-
Creating and Using HTTP Client SDKs in .NET 6
💡 Authentication in OAuth2/OIDC: If you need to manage user and client access tokens I suggest using IdentityModel.AspNetCore. It acquires, caches, and rotates tokens for you, see the docs.
What are some alternatives?
Refit - The automatic type-safe REST library for .NET Core, Xamarin and .NET. Heavily inspired by Square's Retrofit library, Refit turns your REST API into a live interface.
RestSharp - Simple REST and HTTP API Client for .NET
AspNet.Security.OAuth.Providers - OAuth 2.0 social authentication providers for ASP.NET Core
Ocelot - .NET API Gateway
autorest - OpenAPI (f.k.a Swagger) Specification code generator. Supports C#, PowerShell, Go, Java, Node.js, TypeScript, Python
Flurl.Http - Fluent URL builder and testable HTTP client for .NET
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
Simple.OData.Client
RESTFulSense - A RESTFul operations client that serializes responses and throws meaningful exceptions for >= 400 status codes.
AzureFunctions.Extensions.OpenIDConnect - OIDC / JWT Bearer Tokens authentication made easy for Azure Functions. Work with the well known ASPNET Authorize attribute. Compatible with popular identity providers including Auth0, Azure AD B2C, Azure AD, Google etc..