You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* The boundary used is `-` and is passed to the client in the http response's `Content-Type` header. Note that headers can appear in both the HTTP response itself and as part of the response body. The `Content-Type` header must be sent in the HTTP response.
35
-
*Each part of the multipart response must start with `---` and a `CRLF`
31
+
*An initial boundary is sent marking the end of the preamble area.
36
32
* Each part of the multipart response must contain a `Content-Type` header. Similar to the GraphQL specification this specification does not require a specific serialization format. For consistency and ease of notation, examples of the response are given in JSON throughout the spec.
37
-
* Each part of the multipart response must contain a `Content-Length` header. This should be the number of bytes of the payload of the response. It does not include the size of the headers, boundaries, or `CRLF`s used to separate the content.
38
33
* After all headers, an additional `CRLF` is sent.
39
-
* The payload is sent, followed by two`CRLF`s.
40
-
* After the last part of the multipart response is sent, the terminating boundary `-----` is sent, followed by a `CRLF`
34
+
* The payload is sent, followed by a`CRLF`.
35
+
* After each payload, a boundary is sent. For the final payload, the terminating boundary of `-----`followed by a `CRLF`is sent. For all other payloads a boundary of `---`followed by a `CRFL` is sent.
0 commit comments