{"push_id":569138258,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"eec8870ac1eaad03c779550f8ea275ec4f554fbf","before":"d151759f8ace1d02bccddafdd6e2359654893bb1","commits":[{"sha":"eec8870ac1eaad03c779550f8ea275ec4f554fbf","author":{"email":"ab4aee7ec64397770ccef23750fac60773af8962@gmail.com","name":"Tatsuhiro Tsujikawa"},"message":"Fix bug that client may send PROTOCOL_ERROR upon canceled push stream\n\nPreviously we treat stream in NGHTTP2_STREAM_RESERVED state specially,\nthat is we don't increment or decrement streams counts if stream is in\nthat state.  Because of this, we don't change the stream state to\nNGHTTP2_STREAM_CLOSING if stream is in NGHTTP2_STREAM_RESERVED.  But\nit turns out that it causes a problem.  If client canceled pushed\nstream before push response HEADERS, stream is still in\nNGHTTP2_STREAM_RESERVED state.  If push response HEADERS arrived in\nthis state, library happily accepts it and passed to application.\n\nWith this commit, this bug was corrected.  We now change stream state\nto NGHTTP2_STREAM_CLOSING even if it was in NGHTTP2_STREAM_RESERVED\nstate.  We now use NGHTTP2_STREAM_FLAG_PUSH to determine whether we\nhave to increase/decrase stream count.","distinct":true,"url":"https://api.github.com/repos/tatsuhiro-t/nghttp2/commits/eec8870ac1eaad03c779550f8ea275ec4f554fbf"}]}