Mercurial > hg > nginx-quic
annotate src/os/win32/nginx_icon16.xpm @ 7892:2096b21fcd10
gRPC: RST_STREAM(NO_ERROR) handling (ticket #1792).
As per https://tools.ietf.org/html/rfc7540#section-8.1,
: A server can send a complete response prior to the client
: sending an entire request if the response does not depend on
: any portion of the request that has not been sent and
: received. When this is true, a server MAY request that the
: client abort transmission of a request without error by
: sending a RST_STREAM with an error code of NO_ERROR after
: sending a complete response (i.e., a frame with the
: END_STREAM flag). Clients MUST NOT discard responses as a
: result of receiving such a RST_STREAM, though clients can
: always discard responses at their discretion for other
: reasons.
Previously, RST_STREAM(NO_ERROR) received from upstream after
a frame with the END_STREAM flag was incorrectly treated as an
error. Now, a single RST_STREAM(NO_ERROR) is properly handled.
This fixes problems observed with modern grpc-c [1], as well
as with the Go gRPC module.
[1] https://github.com/grpc/grpc/pull/1661
author | Ruslan Ermilov <ru@nginx.com> |
---|---|
date | Thu, 23 Apr 2020 15:10:24 +0300 |
parents | 4ac89c5aa10d |
children |
rev | line source |
---|---|
681 | 1 /* XPM */ |
2 static char * nginx_xpm[] = { | |
3 "16 16 2 2", | |
4 /* colors */ | |
5 " c none", | |
6 "GG c #009900", | |
7 /* pixels */ | |
8 " ", | |
9 " GGGGGGGGGGGGGGGG ", | |
10 " GGGGGGGGGGGGGGGG ", | |
11 " GGGGGGGGGGGGGGGGGGGG ", | |
12 " GGGGGG GGGGGG ", | |
13 " GGGGGG GGGGGG ", | |
14 " GGGGGG ", | |
15 " GGGGGG GGGGGGGGGGGGGGGG ", | |
16 " GGGGGG GGGGGGGGGGGGGGGGGG ", | |
17 " GGGGGG GGGGGGGGGGGGGG ", | |
18 " GGGGGG GGGGGG ", | |
19 " GGGGGG GGGGGG ", | |
20 " GGGGGGGGGGGGGGGGGGGG ", | |
21 " GGGGGGGGGGGGGGGG ", | |
22 " GGGGGGGGGGGGGGGG ", | |
23 " " | |
754
4ac89c5aa10d
style fix: remove trailing spaces
Igor Sysoev <igor@sysoev.ru>
parents:
681
diff
changeset
|
24 }; |