add comment about known bug in .net core 1.1

This commit is contained in:
dsanz 2017-03-28 13:55:27 +02:00
parent 5fed56db51
commit e596926b9b

View File

@ -32,6 +32,8 @@
Messages = new[] { context.Exception.Message } Messages = new[] { context.Exception.Message }
}; };
// Result asigned to a result object but in destiny the response is empty. This is a known bug of .net core 1.1
//It will be fixed in .net core 1.1.2. See https://github.com/aspnet/Mvc/issues/5594 for more information
context.Result = new BadRequestObjectResult(json); context.Result = new BadRequestObjectResult(json);
context.HttpContext.Response.StatusCode = (int)HttpStatusCode.BadRequest; context.HttpContext.Response.StatusCode = (int)HttpStatusCode.BadRequest;
} }
@ -47,6 +49,8 @@
json.DeveloperMeesage = context.Exception; json.DeveloperMeesage = context.Exception;
} }
// Result asigned to a result object but in destiny the response is empty. This is a known bug of .net core 1.1
// It will be fixed in .net core 1.1.2. See https://github.com/aspnet/Mvc/issues/5594 for more information
context.Result = new InternalServerErrorObjectResult(json); context.Result = new InternalServerErrorObjectResult(json);
context.HttpContext.Response.StatusCode = (int)HttpStatusCode.InternalServerError; context.HttpContext.Response.StatusCode = (int)HttpStatusCode.InternalServerError;
} }