Halifax.Http 0.0.4

There is a newer version of this package available.
See the version list below for details.
dotnet add package Halifax.Http --version 0.0.4                
NuGet\Install-Package Halifax.Http -Version 0.0.4                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Halifax.Http" Version="0.0.4" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Halifax.Http --version 0.0.4                
#r "nuget: Halifax.Http, 0.0.4"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Halifax.Http as a Cake Addin
#addin nuget:?package=Halifax.Http&version=0.0.4

// Install Halifax.Http as a Cake Tool
#tool nuget:?package=Halifax.Http&version=0.0.4                
Package Name NuGet
Halifax.Api     NuGet
Halifax.Core     NuGet
Halifax.Domain     NuGet
Halifax.Http     NuGet

Halifax Service Foundation

Simplistic libraries for complex projects. Halifax libraries are designed to speed up API service development process by encapsulating common functionality required for all microservices, allowing developers to focus on the business logic instead of copy-pasting the boilerplate code from project to project. The libraries are focussed on the following aspects of any application:

  • ✅ Exception handling
  • ✅ JWT Authentication
  • ✅ API models
  • ✅ HTTP Communication
  • ✅ Swagger
  • ✅ Logging
  • ✅ CORS

Installation

Install the API library using nuget package with Package Manager Console:

Install-Package Halifax.Api

Or using .NET CLI:

dotnet add package Halifax.Api

Getting Started

Please refer to the Peggy's Cove example API project Startup.cs file for more details but basically all you need is to have this in your startup class:

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddHalifax();
    }

    public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
        app.UseHalifax();
    }
}

This enables routing with controllers and exception handling.

Models

It's very beneficial if all API responses follow the same format. It makes it easier to consume by the clients. In order to achieve it, there is a model called ApiResponse. It's designed to return response data, empty data or error information in the same consistent format. Here are the main use cases:

// Return API response with your model
return ApiResponse.With(model);

// Return empty API response
return ApiResponse.Empty;

When API response is used for all APIs in the project the response will always be of a format:

{
    data: {...} // your model
    success: true/false,
    error: { // null if successful
        type: "ArgumentNullException",
        message: "Email is required",
        trace: "(126) ArgumentNullException was thrown ... (typical exception stack trace)"
    }
}

Exceptions

There are 3 main exception types that can be used out of the box:

  • HalifaxException - resulting in 403 bad request.
  • HalifaxNotFoundException - 404 when resource is not found.
  • HalifaxUnauthorizedException - 401 unauthorized.

These exceptions are handled by Halifax exception handling middleware. Typical use case can look like this:

var user = await context.Users.FirstOrDefaultAsync(u => u.UserId == id);
if (user == null)
{
    throw new HalifaxNotFoundException("User not found");
}

The resulting HTTP response will have a status code 404 and JSON (using ApiResponse models):

{
  "data": null,
  "success": false,
  "error": {
    "message": "User not found"
  }
}

For more advanced scenarios you can override DefaultExceptionHandler or implement and register your own IExceptionHandler.

Configuration

TODO: ...

JWT Authentication

Enable authentication/authorization using the following code. When you AddHalifax dependencies to services on app startup, make this call:

services.AddHalifax(builder => builder
    .ConfigureAuthentication("Your_JWT_secret",
        validateAudience: false,
        validateIssuer: false,
        requireExpirationTime: false));

When this is enabled all your non-[AllowAnonymous] will require "Authentication: Bearer {token}" header. Halifax provides a way to create tokens easily:

var claims = new List<Claim> 
{
    new Claim("ClaimType", "ClaimData"),
    ...
};
var expiration = DateTime.UtcNow.AddDays(90);
var token = Jwt.Create("Your_JWT_secret", claims, expiration);

You can access request token data from HttpContext.User.Claims. To verify that claims are correct there is a helper ClaimsAuthorizeFilterAttribute to override, it can be used for methods and controllers:

internal class MyClaimsAuthorize : ClaimsAuthorizeFilterAttribute
{
    protected override bool IsAuthorized(ActionExecutingContext context, List<Claim> claims)
    {
        // check your claims, return true/false or throw exception.
        // extension methods that can help:
        claims
            .ClaimExpected("ClaimType", "ClaimValue")
            .ClaimIsEmail("ClaimType", out var email);
            // etc.
    }
}

If you need to read a token from string, use Jwt.Read("Your_JWT_secret", token).

MIT License

Copyright (c) 2020 Andrei M

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Product Compatible and additional computed target framework versions.
.NET net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
4.0.0 90 11/19/2024
3.1.4 159 9/10/2024
3.1.3 344 8/7/2024
3.1.2 248 5/10/2024
3.1.1 203 3/11/2024
3.1.0 139 2/11/2024
3.0.1 241 1/24/2024
3.0.0 336 11/17/2023
2.0.8 161 10/30/2023
2.0.7 263 9/14/2023
2.0.6 216 8/16/2023
2.0.5 238 7/9/2023
2.0.4 338 3/23/2023
2.0.3 257 3/20/2023
2.0.2 244 3/20/2023
2.0.1 421 2/24/2023
2.0.0 449 12/21/2022
1.0.3 620 10/16/2022
1.0.2 440 9/21/2022
1.0.1 513 8/19/2022
1.0.0 531 7/11/2022
0.0.9 564 6/22/2022
0.0.8 423 6/22/2022
0.0.7 420 6/22/2022
0.0.6 554 6/10/2022
0.0.5 410 6/10/2022
0.0.4 423 6/10/2022
0.0.3 461 6/2/2022
0.0.2 411 6/2/2022
0.0.1 419 6/2/2022

v0.x.x - Initial release