All Versions
34
Latest Version
Avg Release Cycle
65 days
Latest Release
515 days ago

Changelog History
Page 1

  • v1.7.1 Changes

    May 29, 2020

    🚀 See the full release notes

  • v1.7.0 Changes

    November 01, 2019
    • ➕ Add possibility for request with content (like POST, PUT ...) to use methods : WithBasicAuthentication WithOAuthBearer WithTimeout WithETagContainer.
    • 👍 Allow non 2xx response (see sample below)

    👍 Allow non http 2xx responses

    Globaly

    👍 Allow any status codes :

    client.Settings.HttpStatusCodeAllowed.AllowAnyStatus = true;

    👍 Allow only a range of http status codes :

    client.Settings.HttpStatusCodeAllowed.Add(new HttpStatusRange(400, 420));

    or

    client.Settings.HttpStatusCodeAllowed.Add(new HttpStatusRange(System.Net.HttpStatusCode.BadRequest, System.Net.HttpStatusCode.BadGateway));

    By request

    👍 Allow all status code :

    request.AllowAllHttpStatusCode().ExecuteAsync();

    👍 Allow only a range of http status codes :

    request.AllowRangeHttpStatusCode(400, 420).ExecuteAsync();

    👍 Allow only on stats code of http status codes :

    request.AllowSpecificHttpStatusCode(409).ExecuteAsync();

  • v1.6.6 Changes

    October 16, 2019

    🚀 See the full release notes

  • v1.6.5 Changes

    October 16, 2019

    🚀 See the full release notes

  • v1.6.4 Changes

    August 13, 2019

    🚀 See the full release notes

  • v1.6.3 Changes

    May 21, 2019
    • Now calculate dynamically the headers to add to resquest.

    In this sample we get a custom token and add it to all our requests => 

    client.Settings.CalculateHeadersHandler = async () =>
{
   var token = await GetACustomTokenAsync();

   var headers = new Headers
   {
       { "CustomToken", token },
   };
   return headers;
};

  • v1.6.2 Changes

    May 04, 2019
    • Now HttpException expose the headers of the response
    • Constructor of HttpException is now internal
    • ➕ Add possibility to encapsulate HttpException automatically.

    We can setup a global handler to provide a logic to encapsulate HttpException automatically. For example I can choose to translate all HttpException with StatusCode NotFound in a NotFoundCustomException.

    client.Settings.EncapsulateHttpExceptionHandler = (ex) =>
{
   if (ex.StatusCode == System.Net.HttpStatusCode.NotFound)
   {
      return new NotFoundCustomException();
   }

   return ex;
};

    👻 Now if I call an API wich respond with status code NotFound it will throw automaticaly my custom exception.

    // Call an API wich throw NotFound error
await client.GetRequest("APIWhichNotExists").ExecuteAsync();

  • v1.6.1 Changes

    January 21, 2019

    🚀 See the full release notes

  • v1.6.0 Changes

    October 27, 2018
    • ➕ Add support of Entity Tag (ETag)

    0️⃣ ETag is not enabled by default to enable it :

    client.Settings.ETagContainer = new ETagFileContainer(@"C:\ETagFolder");

    You can also enable on only on specific request like below :

    request.WithETagContainer(eTagContainer);
    • ➕ Add support of string content (for mono part and multipart requests) cs request.AddStringContent("myContent").ExecuteAsycnc();
    • Now the assembly is strong named

  • v1.5.5 Changes

    October 18, 2018

    🚀 See the full release notes