Microsoft Owin Response Body Encoding

Asked May 13 '16 at 15:58

Active Sep 04 '18 at 21:43

Viewed 492 times

In my OwinMiddleware I just write out to the body:

await context.Response.Body.WriteStringAsync("Hey There");

The raw response I get in Fiddler is:

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Server: Microsoft-HTTPAPI/2.0
Date: Fri, 13 May 2016 16:00:07 GMT

A
/hey/there
5
there
9
Hey There
26
{ec86d5c7-4ea4-437f-be2a-4e294b655227}
0

And Fiddler is saying this encoded (with a message saying please click here decode)

The single letters and numbers are not mine. I wrote /hey/there and there and Hey There and the Guid with braces.

How do I just get the plain text response?

edited Sep 04 '18 at 21:43

Oscar Cabrero

4,168
8
29
49

asked May 13 '16 at 15:58

Callum Linington

14,213
12
75
154

It looks like you are getting a plain-text response. It's just using chunked encoding. Each individual string you're sending is getting sent to the client immediately (with a leading length indicator, per the rules of chunked encoding). – Joe White May 13 '16 at 16:01
Yeah okay, so I shall just change the way I write to the stream then – Callum Linington May 13 '16 at 16:03
@CallumLinington why? The client should be able to handle the response even if it's chunked. – Panagiotis Kanavos May 13 '16 at 16:04
@PanagiotisKanavos yeah that is also a very good point – Callum Linington May 13 '16 at 16:04
No problem here. Move along. – spender May 13 '16 at 16:11

Microsoft Owin Response Body Encoding

0 Answers0