Proposed new status code for GOAWAY/RST_STREAM errors: INTERNAL_ERROR

[William Chan (陈智昌)]

Basically, for situations where we detect an internal error, not caused by the peer, I'd like to use INTERNAL_ERROR. Currently, the best alternative is the generic PROTOCOL_ERROR. An example of a situation where I'd like to use this is when we detect a flow control window size accounting error and need to terminate the stream with a RST_STREAM. I think it'd be nice to use a INTERNAL_ERROR status code rather than PROTOCOL_ERROR. I am electing not to use FLOW_CONTROL_ERROR since that currently indicates that the peer is at fault.

[Roberto Peon]

How would the other side respond differently to such as compared to any other error code? If the answer is it wouldn't really be different, all we are adding is ambiguity.

[Mike Belshe]

I agree with Will, and I've added INTERNAL_ERROR to both RST_STREAM and GOAWAY.

To answer Roberto's question:  the handling of INTERNAL_ERROR and PROTOCOL_ERROR is the same.  However, having both codes is helpful for debugging to understand where a failure occurred.  Neither one is recoverable.

Mike