OkObjectResult with string value outputs plain text only, no json.

[aliveli186]

[HttpGet]
public IActionResult GetInfo()
{
    var info = "Hello";

    return Ok(info);
}

The method above always returns plain text (Hello) content instead of ("Hello") even if the request has "Accept: application/json" header.

[rynowak]

Is the response "Hello" or Hello? The former is valid JSON.

[aliveli186]

There response is always: Hello
I expect: "Hello"

[Eilon]

@dougbu if this looks like a bad regression we should consider patching it, so let me know.

[dougbu]

I'm unable to reproduce this with ASP.NET Core, testing both the released 2.0.0 and current dev. @aliveli186 please provide a repro for what you've described, preferably in a GitHub repo.

What I'm seeing

For example the PowerShell command curl -headers @{ Accept = 'text/json' } http://localhost:2092/Home/GetInfo shows the service returns "Hello" in the body -- including the quotation marks. The returned Content-type header correctly matches the request. And, the same thing works when requesting application/json.

The action returns bare Hello with Content-Type: text/plain only if the Accept header

• is missing,
• includes text/plain,
• includes a broader wildcard e.g. */*, or
• includes only unsupported content types e.g. just application/xml when XML formatters are not enabled.

[rynowak]

@aliveli186 - what's your startup code look like (just need the ConfigureServices). Are you using AddMvc()?

[aliveli186]

@rynowak Yes I'm using AddMvc().

services.AddMvc()
        .AddJsonOptions(options => options.SerializerSettings.ContractResolver = new DefaultContractResolver());

AddJsonOptions has no effect on the result.

[aliveli186]

@dougbu By the way this happens in: netcoreapp1.1
Couldn't test it in netcoreapp2.0 because IIS Express in not launching somehow.
Fiddler screenshot of the request and response: http://imgur.com/0IHSnps

[dougbu]

Ah, that explains why I can't hit this using 2.0.0! You're hitting #4945 and we fixed that issue in 2.0.0.

The 1.1.x workaround is to add the following to the AddMvc() call in your ConfigureServices() method:

services.AddMvc(options => options.OutputFormatters.RemoveType<StringOutputFormatter>());

@Eilon I suspect the behaviour changes we made for #4945 were thought too significant for a patch. But, perhaps we should reconsider? (The recent #6657 issue also touched on the new behaviour.)

[Eilon]

Yeah I don't see how we'd patch that, it's a pretty significant change.

[Eilon]

Given that I don't see a reasonable way to patch in 1.x, and there's an easy to use workaround, and that it's fixed in 2.0, I'm closing this issue. Thanks!

[delraydavis]

unless I am not understanding the issue, I think adding the [Produces("application/json")] decorator to the class should address the problem