Consumes and Produces attributes are ignored in ASP .NET Core Web API

I’m using NSwag.AspNetCore v13.0.6 (latest version as of this writing), and NSwag seem to be ignoring the Consumes and Produces attributes.

Am I missing anything?

[HttpPost("/api/stuff")]
[Consumes("text/plain")]
[Produces("text/plain")]
public IActionResult PostStuff()
{
    return Ok();
}

Relates to #420

[ThomasBaechlerConti]

I am still having this issue. Since this issue claims that everything is correct, I investigated further.

I have an operation that is supposed to consume application/octet-stream, and I have a matching input processor.

[HttpPost]
[Consumes("application/octet-stream")]
public string EndpointConsumesBinaryData([FromBody] byte[] data)
{
    return string.Empty;
}

internal sealed class BinaryInputFormatter : InputFormatter
{
    public BinaryInputFormatter()
    {
        SupportedMediaTypes.Add(MediaTypeHeaderValue.Parse("application/octet-stream"));
    }

    public override async Task<InputFormatterResult> ReadRequestBodyAsync(InputFormatterContext context)
    {
        using var mem = new MemoryStream();
        await context.HttpContext.Request.Body.CopyToAsync(mem);
        return InputFormatterResult.Success(mem.ToArray());
    }

    protected override bool CanReadType(Type type)
    {
        return type.IsAssignableFrom(typeof(byte[]));
    }
}

I registered this input processor and the ASP.NET Core API explorer lists the operation correctly. Even NSwag seems to pick up the Consumes attribute. I created a Document Processor and put a breakpoint in the Process method.

Looking at DocumentProcessorContext.Document.Operations[0].Operation, I see that the ActualConsumes property contains “application/octect-stream”, but the RequestBody.Content dictionary only contains an “application/json” content.

So, in conclusion, NSwag does ignore the consumes attribute and seems to always assume application/json.

[ptr1120]

the same problem on my side, ConsumesAttribute completely ignored.