Question about the "Added empty state UI for payloads, so no more guessing if there is some error or the payload is really empty" feature in 3.3 I'm using 3.3 and I don't see an empty body state, but before filing a bug I want to make sure it's actually a bug and not my misinterpretation. For example, in Chucker I see a response of this:

X-Content-Type-Options: nosniff 
X-XSS-Protection: 1; mode=block 
Cache-Control: no-cache, no-store, max-age=0, must-revalidate 
Pragma: no-cache 
Expires: 0 
Strict-Transport-Security: max-age=2100 ; includeSubDomains 
X-Frame-Options: DENY 
Date: Fri, 02 Oct 2020 01:22:11 GMT 
Transfer-Encoding: chunked 
Connection: keep-alive

in Charles I see this

HTTP/1.1 200 
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
Strict-Transport-Security: max-age=2100 ; includeSubDomains
X-Frame-Options: DENY
Date: Fri, 02 Oct 2020 01:22:11 GMT
Transfer-Encoding: chunked
Connection: keep-alive

In this case, the payload to me is "empty" but I don't see an empty state. Is this because I still have headers? Will I see empty state if headers are missing as well?

Is this because I still have headers?

Correct. We show an empty state if you have no header and no body. The rationale is to avoid having to show a blank page. As soon as there is a body or a header to show, we show it (and we don’t display the empty box icon).

Got it. Thanks for clarification