RE: trailers and pseudo-headers

>>>There are many cases where a server would say "200", and then start a

>>>complicated process that might fail half-way. In HTTP/1.1, signalling

>>>an error in this situation is hard (abort the chunked transfer or close

>>>the connection). It would be good if HTTP/2 can do better here.



I agree.



>> I thought that was what RST_STREAM was for ?

>

> Well, yes, we can say "something went wrong", but that's all.



Technically you can "say" 12 different "wrongs" with the error codes [1] (and one "no wrong").



Why not have an optional error message like the "additional debug data" in GOAWAY?



e.g.



  0                   1                   2                   3

  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

|                        Error Code (32)                        |

+---------------------------------------------------------------+

|                  Additional Error Data (*)                    |

+---------------------------------------------------------------+





[1] http://http2.github.io/http2-spec/#ErrorCodes





This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.