- 07 Dec, 2017 2 commits
-
-
Mikio Hara authored
Change-Id: I7c88abdd74effca1cd8dd72970f0bee914e82fc2 Reviewed-on: https://go-review.googlesource.com/82457 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
Mikio Hara authored
Fixes golang/go#22301. Change-Id: I29f4f8806e10aad59cf7f984fd346acc216b0fd0 Reviewed-on: https://go-review.googlesource.com/79855 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Tobias Klauser <tobias.klauser@gmail.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
- 29 Nov, 2017 1 commit
-
-
Brad Fitzpatrick authored
Updates golang/go#22927 Change-Id: I813b9ba92f9dd7e517385dc95df20691efee01a6 Reviewed-on: https://go-review.googlesource.com/80755Reviewed-by: Benny Siegert <bsiegert@gmail.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
- 28 Nov, 2017 5 commits
-
-
Tom Bergan authored
That test makes a request with no body and receives a response with no body. The client will receive a HEADERS frame with END_STREAM. The test assumes that the stream is closed immediately on receipt of that HEADERS frame, i.e., before RoundTrip returns. This assumption was broken by https://golang.org/cl/70510, which made stream closure asynchronous w.r.t. RoundTrip. To fix TestCloseIdleConnections_h2 while preserving the intent of CL 70510, we break processHeaders into two cases: 1. The request has a body. In this case, END_STREAM puts the stream in a half-closed-remote state, which means the connection is not necessarily idle when RoundTrip returns (since the request body is still being uploaded). In this case, we preserve the behavior from CL 70510. 2. The request does not have a body. In this case, END_STREAM puts the stream in a closed state and we must close the stream before returning from RoundTrip. The following command passes when this CL is merged into net/http: go test -count=100000 -run=TestCloseIdleConnections_h2 net/http Updates golang/go#22413 Change-Id: Iff2a0685a636ad51bff380e86a42b0d0eea984e5 Reviewed-on: https://go-review.googlesource.com/80139 Run-TryBot: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
Gregory Man authored
In invalid response tests logger write error messages to stderr and spam test output. Since we know response are invalid in these tests we can safely discard logger output. Fixes golang/go#22850 Change-Id: Id8c97be910f0cf7dbe2380ba632960364bc8478b Reviewed-on: https://go-review.googlesource.com/80235Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Brad Fitzpatrick authored
Go 1.8 doesn't have t.Helper. Fix the row of red on the dashboard. Change-Id: I85d4bb9fe38e989dc3b6a4e99705599745b83cef Reviewed-on: https://go-review.googlesource.com/80140 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Tom Bergan authored
AFAICT, activeRes serves no real purpose. It is used in just two ways: - To reduce the number of calls to closeIfIdle, which reduces the number of acquires of cc.mu when there are many concurrent streams. I dug through the CL history and could not find any benchmarks showing that this is necessary. - To avoid redundant calls to cs.bufPipe.CloseWithError(err) when a read loop is shutdown. This is unnecessary, since redundant CloseWithError calls are ignored. Since there isn't a good reason to have activeRes, the simplest way to fix the leak is to remove activeRes entirely. Updates golang/go#21543 Change-Id: I1d1d2dc6c946425a2772c8bf71436707021ac269 Reviewed-on: https://go-review.googlesource.com/80137Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Tom Bergan authored
This change was originally made in https://golang.org/cl/46631, however, that change was applited to net/http/h2_bundle.go instead of x/net/http2. Updates golang/go#20784 Change-Id: I947fa4c19f3efc400856573768140bece28276a2 Reviewed-on: https://go-review.googlesource.com/80135 Run-TryBot: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
- 27 Nov, 2017 3 commits
-
-
Brad Fitzpatrick authored
Tests are in net/http. (upcoming CL) Updates golang/go#22880 Change-Id: Ie94693ad4e14f0c07926a0b6c7827caace94a0aa Reviewed-on: https://go-review.googlesource.com/80076Reviewed-by: Tom Bergan <tombergan@google.com> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Tom Bergan authored
This fixes TestTrailersClientToServer_h2. Before this CL, the following command reliably fails. With this CL merged into net/http, the following command reliably succeeds. go test -race -run=TestTrailersClientToServer_h2 -count 1000 net/http Updates golang/go#22721 Change-Id: I05d1504c60854fcf3ae9531f36a126e94b00f0b7 Reviewed-on: https://go-review.googlesource.com/79238Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Emmanuel Odeke <emm.odeke@gmail.com>
-
Brad Fitzpatrick authored
In golang/go#22880, our http2 server was sending a HEADERS response without a :status header. Our client code correctly returned an error from RoundTrip, but we forgot to clean up properly, and then subsequently crashed on a DATA frame. This fixes the Transport crash. A fix for the server bug will come separately. Change-Id: Iea3bcf4a8c95963c8b5e2b6dd722177607bd1bc1 Reviewed-on: https://go-review.googlesource.com/80056 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Tom Bergan <tombergan@google.com>
-
- 23 Nov, 2017 1 commit
-
-
Roger Peppe authored
This factors out the HTTP proxy functionality from net/http, with a view to vendoring it into net/http later. See discussion in https://go-review.googlesource.com/c/go/+/68091 Change-Id: I8df8a92a13bca03504edd24b71a9a184f290b87d Reviewed-on: https://go-review.googlesource.com/76910Reviewed-by: roger peppe <rogpeppe@gmail.com>
-
- 22 Nov, 2017 1 commit
-
-
Brad Fitzpatrick authored
Updates golang/go#18776 Change-Id: I7568f779e2b86c72c54c8744c08cc02988dde55b Reviewed-on: https://go-review.googlesource.com/79498 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Tom Bergan <tombergan@google.com>
-
- 15 Nov, 2017 1 commit
-
-
Frederic Guillot authored
This code snippet should contains the prefix "html" like other examples to be consistent. Change-Id: I32428452625c016894aebc2011cde2dd614e6ed9 Reviewed-on: https://go-review.googlesource.com/77830Reviewed-by: Gabriel Aszalos <gabriel.aszalos@gmail.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Gabriel Aszalos <gabriel.aszalos@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 07 Nov, 2017 1 commit
-
-
Anmol Sethi authored
The HTTP/2 RFC does indeed mandate TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 but in practice, people are also using TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 becuase they are only using an ECDSA certificate. This is the case in acme/autocert. It doesn't make sense to enforce only RSA in cipher suites if it will never be used because they are using a ECDSA certificate. Change-Id: I86dac192a3eb9b74e4268310a3b550b3bd88a37f Reviewed-on: https://go-review.googlesource.com/30721Reviewed-by: Tom Bergan <tombergan@google.com> Run-TryBot: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 02 Nov, 2017 2 commits
-
-
Tom Bergan authored
Based on golang/go#19653, it should be possible to reuse an http.Request object after the outstanding request has completed. This CL fixes a race in the http/2 library that occurs when a caller tries to reuse an http.Request just after the request completed. The new test failed with -race before this CL and passes after this CL. Verified with -count 10000. Updates golang/go#21316 Change-Id: I014cf9cefd0dd21f6f41763ba554d23ddc7fca40 Reviewed-on: https://go-review.googlesource.com/75530Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Marcel van Lohuizen authored
See CL 73730: avoid memory leak in validation codes Upstream at 8253218a. Change-Id: I3d4860989c8e057f9cc4c9087a78c9c800c5aa7d Reviewed-on: https://go-review.googlesource.com/74954Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
- 01 Nov, 2017 1 commit
-
-
Tom Bergan authored
There was a case where we forgot to undo this wrapper. Instead of fixing that case, I moved the implementation of ClientConn.RoundTrip into an unexported method that returns the same info as a bool. Fixes golang/go#22136 Change-Id: I7e5fc467f9c26fb74b9b83f2b3b7f8882645e34c Reviewed-on: https://go-review.googlesource.com/75252Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 27 Oct, 2017 1 commit
-
-
Ben Burkert authored
Add an AppendPack method to Message that appends the message data into a byte buffer. Reusing a buffer allows for a reduction in allocations. name time/op Pack-8 5.04µs ± 1% AppendPack-8 4.95µs ± 2% name alloc/op Pack-8 6.22kB ± 0% AppendPack-8 5.71kB ± 0% name allocs/op Pack-8 21.0 ± 0% AppendPack-8 20.0 ± 0% Change-Id: I8bb6b07787cf2ba9ef32e1e60a3003a585ec55be Reviewed-on: https://go-review.googlesource.com/45274Reviewed-by: Ian Gudger <igudger@google.com> Reviewed-by: Mikio Hara <mikioh.mikioh@gmail.com> Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 26 Oct, 2017 1 commit
-
-
Russ Cox authored
The macOS kernel reliably crashes in a repeated TestRouteMessage. Putting some extra padding into the request buffer avoids the crash. This will do as workaround; the kernel bug will be reported to Apple separately. Fixes golang/go#22456. Change-Id: I789d3d57fbc511016d9f4a3fa7662d6c7642f137 Reviewed-on: https://go-review.googlesource.com/73690 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Austin Clements <austin@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 24 Oct, 2017 1 commit
-
-
Marcel van Lohuizen authored
Generated from x/text. Significant changes in the interpretation of the Bidi rule as well as sharpening of the leading dot rules, among other things. Issue golang/go#21471 Change-Id: I8649a4090e2bc530aad4412210a3de344fb2eab6 Reviewed-on: https://go-review.googlesource.com/63951 Run-TryBot: Marcel van Lohuizen <mpvl@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Nigel Tao <nigeltao@golang.org>
-
- 23 Oct, 2017 2 commits
-
-
Michael Fraenkel authored
If a server returns a DATA frame while procesing a HEAD request, the client will discard the data. Fixes golang/go#22376 Change-Id: Ief9c17ddfe51cc17f7f6326c87330ac9d8b9d3ff Reviewed-on: https://go-review.googlesource.com/72551 Run-TryBot: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Tom Bergan <tombergan@google.com>
-
Francisco Rojas authored
Fixes golang/go#22322 Change-Id: I1f0c62ce1c247b583de51faef8722d07e627b441 Reviewed-on: https://go-review.googlesource.com/72570Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 20 Oct, 2017 1 commit
-
-
Tom Bergan authored
Currently, we close the connection immediately after sending a GOAWAY frame if all outstanding responses have been completely sent. However, the client may have had requests in-flight at that time which have been queued in the kernel receive buffer. On both Windows and Linux, if the connection is close()'d when the receive buffer is not empty, the kernel sends RST. This has the effect of aborting both sides of the connection, meaning the client may not actually receive all responses that were sent before the GOAWAY. Instead, we should delay calling close() until after the receive buffer has been drained. We don't want to delay indefinitely, which means we need some kind of timeout. Ideally that timeout should be about 1 RTT + epsilon, under the assumption that the client will not send any more frames after receiving the GOAWAY. However, 1 RTT is difficult to measure. It turns out we were already using a 1 second delay in other cases, so we reuse that same delay here. Note that we do not call CloseWrite() to half-close the underlying TLS connection. This seems unnecessary -- GOAWAY is effectively a half-close at the HTTP/2 level. Updates golang/go#18701 (fixes after it's bundled into net/http) Change-Id: I4d68bada6369ba95e5db02afe6dfad0a393c0334 Reviewed-on: https://go-review.googlesource.com/71372 Run-TryBot: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>
-
- 19 Oct, 2017 1 commit
-
-
Joe Kyo authored
Change-Id: I7091af7efe71d46a0f55fd8341afcaa76073adaf Reviewed-on: https://go-review.googlesource.com/71630Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
- 16 Oct, 2017 1 commit
-
-
Anand K. Mistry authored
When a client receives a HEADER frame with a END_STREAM flag, clientConn.streamByID closes the stream before processing the headers which may contain a full non-error response. This causes the request's bodyWriter cancelation to race with the response. Closing the stream after processing headers allows the response to be available before the bodyWriter is canceled. Updates golang/go#20521 Change-Id: I70740e88f75240836e922163a54a6cd89535f7b3 Reviewed-on: https://go-review.googlesource.com/70510 Run-TryBot: Emmanuel Odeke <emm.odeke@gmail.com> Reviewed-by: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 04 Oct, 2017 2 commits
-
-
Mikio Hara authored
On android, runtime.GOOS returns "android" instead of "linux". Fixes golang/go#22115. Change-Id: Idd24d5602f8fa9be1fca0b64bd8966849ea2b5e7 Reviewed-on: https://go-review.googlesource.com/67770Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
Fixes golang/go#22117. Change-Id: I0d9c3e126aaf97cd297c84e064e9a521ddac626f Reviewed-on: https://go-review.googlesource.com/67750Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 27 Sep, 2017 1 commit
-
-
Kevin Burke authored
Move the README to README.md so Gerrit can render it; currently Gerrit only renders files named exactly "README.md" (for example at https://go.googlesource.com/go). Add more links to the README explaining how to file issues, how to submit code changes, where to download the code to and how to get it. Hopefully this should help people who go to https://go.googlesource.com/net or https://github.com/golang/net figure out how to get started with development. Change-Id: I4eb54f2b210e4f028c9f00955ff19b55643315e6 Reviewed-on: https://go-review.googlesource.com/49850Reviewed-by: Mikio Hara <mikioh.mikioh@gmail.com>
-
- 26 Sep, 2017 1 commit
-
-
Kunpei Sakai authored
Some elements and attributes have been removed from the spec, but are kept here for backwards compatibility. Also, this makes gen.go support go:generate and write contents into target files directly. Finally, this makes `go generate` work on an entire directory. Change-Id: I8d41840eec69eec1ef08527d8d71786612a3121d Reviewed-on: https://go-review.googlesource.com/65152 Run-TryBot: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Tom Bergan <tombergan@google.com>
-
- 22 Sep, 2017 1 commit
-
-
Joe Kyo authored
RFC 1929 describes the SOCKS5 username/password authentication method. The proxy package implements this method, but doesn't mention RFC 1929. This change adds mention of RFC 1929. Change-Id: I30487fb41c1baa16b6ee8a99210168a597e5cb65 Reviewed-on: https://go-review.googlesource.com/60870Reviewed-by: Mikio Hara <mikioh.mikioh@gmail.com> Reviewed-by: Avelino <t@avelino.xxx> Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 20 Sep, 2017 3 commits
-
-
namusyaka authored
Also, the isindex element has been remove from specification, so this commit adds a comment about it. Change-Id: I79a9b1eb9dae8274e2ca498ab73b2e73521d54e9 Reviewed-on: https://go-review.googlesource.com/64230Reviewed-by: Tom Bergan <tombergan@google.com> Run-TryBot: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Volker Dobler authored
The number of children (494) got pretty close to the available maximum number of children (511) in the table. This number increased over the last year by roughly 65 indicating that we would run out of space in the next three months. The other fields still have enough room left. The following table show the growth over the last 1.5 years: # Commit Date Children TextOffset Length High Low b05061f 2017-09-18 494 28750 36 8407 8402 859d1a86 2017-09-06 494 28750 36 8407 8402 ddf80d09 2017-06-14 479 28411 36 8262 8257 61557ac0 2017-01-26 466 28023 36 8121 8120 5695785b 2016-10-20 434 27930 36 8135 8134 07b51741 2016-08-11 424 27866 36 8062 8051 7864c9ee 2016-07-07 421 27811 36 8049 8038 3f122ce3 2016-06-09 417 27680 36 8029 8018 d58ca661 2016-03-04 409 27059 36 7887 7886 6c581b96 2016-02-01 406 26999 36 7868 7867 78e1654e 2016-01-20 405 26986 36 7863 7862 Given this rate of grow of max text offset it will overflow in 2021. Thus use the last of the available 32 bits to encode more children. Change-Id: I04db02100b202f220a0b4ee509f868db031fd8ab Reviewed-on: https://go-review.googlesource.com/64330Reviewed-by: Nigel Tao <nigeltao@golang.org>
-
Avelino authored
Change-Id: I557b34aeabf0dc838f9c574966c2d12f02e41a19 Reviewed-on: https://go-review.googlesource.com/57332Reviewed-by: Tom Bergan <tombergan@google.com>
-
- 15 Sep, 2017 1 commit
-
-
namusyaka authored
a -> an Change-Id: I7d0413396e51f16e0a83732a07a5536548e03506 Reviewed-on: https://go-review.googlesource.com/63992Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 14 Sep, 2017 1 commit
-
-
Volker Dobler authored
Update the list to revision 38b238d6324042f2c2e6270459d1f4ccfe789fba (2017-08-28T20:09:01Z). Change-Id: I80aca3aa21255176e0b6a4c3f8b1b755d0ee2c8e Reviewed-on: https://go-review.googlesource.com/61890Reviewed-by: Nigel Tao <nigeltao@golang.org> Run-TryBot: Nigel Tao <nigeltao@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 12 Sep, 2017 1 commit
-
-
Hiroaki Nakamura authored
Change-Id: I1011371968c2a548378c7490212a39989a9de75e Reviewed-on: https://go-review.googlesource.com/38284 Run-TryBot: Marcel van Lohuizen <mpvl@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Marcel van Lohuizen <mpvl@golang.org>
-
- 28 Aug, 2017 1 commit
-
-
Mike Appleby authored
Add a new peerMaxHeaderListSize member to ClientConn which records the SETTINGS_MAX_HEADER_LIST_SIZE requested by the client's peer, and respect this limit in (*ClientConn) encodeHeaders / encodeTrailers. Attempting to send more than peerMaxHeaderListSize bytes of headers or trailers will result in RoundTrip returning errRequestHeaderListSize. Updates golang/go#13959 Change-Id: Ic707179782acdf8ae543429ea1af7f4f30e67e59 Reviewed-on: https://go-review.googlesource.com/29243 Run-TryBot: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Tom Bergan <tombergan@google.com>
-
- 24 Aug, 2017 1 commit
-
-
Olivier Poitrey authored
If the server returns a DATA frame before a HEADERS frame, the client must close the connection with a PROTOCOL_ERROR as describe in the section 8.1.2.6. The current implementation does not reject such sequence and panics trying to write on the non-initialized bufPipe. Fixes golang/go#21466 Change-Id: I55755dba259d026529a031e9ff82c915f5e4afae Reviewed-on: https://go-review.googlesource.com/56770Reviewed-by: Tom Bergan <tombergan@google.com> Run-TryBot: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 09 Aug, 2017 1 commit
-
-
Tom Bergan authored
Currently if the http2.Transport hits SettingsMaxConcurrentStreams for a server, it just makes a new TCP connection and creates the stream on the new connection. This CL updates that behavior to instead block RoundTrip until a new stream is available. I also fixed a second bug, which was necessary to make some tests pass: Previously, a stream was removed from cc.streams only if either (a) we received END_STREAM from the server, or (b) we received RST_STREAM from the server. This CL removes a stream from cc.streams if the request was cancelled (via ctx.Close, req.Cancel, or resp.Body.Close) before receiving END_STREAM or RST_STREAM from the server. Updates golang/go#13774 Updates golang/go#20985 Updates golang/go#21229 Change-Id: I660ffd724c4c513e0f1cc587b404bedb8aff80be Reviewed-on: https://go-review.googlesource.com/53250 Run-TryBot: Tom Bergan <tombergan@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-