Исходное сообщение
"HTTP/2.0 получил статус предложенного стандарта" Отправлено Crazy Alex, 18-Фев-15 17:15
1) A client can use the SETTINGS_MAX_CONCURRENT_STREAMS setting to limit    the number of responses that can be concurrently pushed by a server.    Advertising a SETTINGS_MAX_CONCURRENT_STREAMS value of zero disables    server push by preventing the server from creating the necessary    streams.  This does not prohibit a server from sending PUSH_PROMISE    frames; clients need to reset any promised streams that are not    wanted. 2)  If the client determines, for any reason, that it does not wish to    receive the pushed response from the server, or if the server takes    too long to begin sending the promised response, the client can send    an RST_STREAM frame, using either the CANCEL or REFUSED_STREAM codes,    and referencing the pushed stream's identifier.

Ваше сообщение
Имя*:
EMail:	Для отправки ответов на email укажите знак ! перед адресом, например, !user@host.ru (!! - не показывать email). Более тонкая настройка отправки ответов производится в профиле зарегистрированного участника форума.
Заголовок*:
Сообщение*:	> 1) A client can use the SETTINGS_MAX_CONCURRENT_STREAMS setting to limit > the number of responses that can be concurrently pushed > by a server. > Advertising a SETTINGS_MAX_CONCURRENT_STREAMS value of zero disables > server push by preventing the server from creating the > necessary > streams. This does not prohibit a server from > sending PUSH_PROMISE > frames; clients need to reset any promised streams that > are not > wanted. > 2) If the client determines, for any reason, that it does > not wish to > receive the pushed response from the server, or if > the server takes > too long to begin sending the promised response, the > client can send > an RST_STREAM frame, using either the CANCEL or REFUSED_STREAM > codes, > and referencing the pushed stream's identifier.
	Введите код, изображенный на картинке: