I see this as a case of EOF before a well-formed JSON could be decoded. Not sure why it deserves special treatment.
Now, why it thinks JSON should be there. Maybe the server filled the headers first, in anticipation what the type of response is going to be, then later figured out the request is malformed, and aborted with HTTP 400 (Bad Request) without having cleared the header.
If the headers don't say that, then, of course, the client-side pipeline is broken.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2019-10-22 02:28 pm (UTC)Now, why it thinks JSON should be there. Maybe the server filled the headers first, in anticipation what the type of response is going to be, then later figured out the request is malformed, and aborted with HTTP 400 (Bad Request) without having cleared the header.
If the headers don't say that, then, of course, the client-side pipeline is broken.