- 24 Oct, 2016 4 commits
-
-
Tom Bergan authored
Fix spec bug: Section 5.3.1 says that self-dependencies should be treated as a stream error of type PROTOCOL_ERROR. Updates golang/go#16046 Change-Id: I8b5dc8808943dc96aac0c543c7032fa989ab9e0b Reviewed-on: https://go-review.googlesource.com/31858Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Brad Fitzpatrick authored
Don't do async frame writes when the write is known to be small enough to definitely fit in the write buffer and not cause a flush (which might block). This avoids starting a new goroutine and doing a channel send operation for many frame writes. name old time/op new time/op delta ServerGets-4 146µs ± 2% 144µs ± 1% -1.46% (p=0.000 n=14+14) ServerPosts-4 162µs ± 1% 160µs ± 1% -1.15% (p=0.000 n=15+15) Server_GetRequest-4 145µs ± 1% 143µs ± 0% -1.26% (p=0.000 n=15+15) Server_PostRequest-4 160µs ± 1% 158µs ± 1% -1.32% (p=0.000 n=15+15) The headers frame is the main last one which might show some benefit if there's a cheap enough way to conservatively calculate its size. Change-Id: I9be2ddbf04689340819d8701ea671fff378d9e79 Reviewed-on: https://go-review.googlesource.com/31495 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
Tom Bergan authored
This adds an interface to support pluggable schedulers. The interface is defined in writesched.go. The only type needed by this interface is FrameWriteRequest, which describes a request to write a frame (this used to be called frameWriteMsg). The scheduler can be configured with a new field in http2.Server. Two schedulers are implemented: 1) A random scheduler that is essentially equivalent to the existing scheduler. This is currently the default scheduler if none is configured. The implementation is in writesched_random.go. 2) A scheduler that uses H2 weights and priorities. The H2 priority tree is maintained as a tree of priorityNodes. The next frame is chosen by walking this tree in topological order, where sibling nodes are ordered by their bandwidth usage relative to their H2 weight. Two optional features are added to improve performance -- these are configured with PriorityWriteSchedulerConfig. Fixes golang/go#16168 Change-Id: I97ec93e5c58c2efec35455ba2f3c31e849f706af Reviewed-on: https://go-review.googlesource.com/25366Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Nigel Tao authored
Update the list to revision 915565885d0fbd25caf7d8b339cd3478f558da94 (2016-10-19T08:16:09Z). Change-Id: Ie94e7237015f2d84e0a0d082bd7ff9e04b05ecd9 Reviewed-on: https://go-review.googlesource.com/31530Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
- 23 Oct, 2016 1 commit
-
-
Brad Fitzpatrick authored
Also remove some stale TODOs and finish one of the TODOs, ignoring more incoming frames when the connection is in GOAWAY mode. Also, fix independently-broken transport test from a change in std: https://golang.org/cl/31595 Updates golang/go#14204 Change-Id: Iae8b02248464d613979c30d8f86eacb329cd262f Reviewed-on: https://go-review.googlesource.com/31727Reviewed-by: Ian Lance Taylor <iant@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
-
- 22 Oct, 2016 1 commit
-
-
Luka Zakrajšek authored
Displayname WebDAV property should be XML escaped. With current implementation a file with name '<.txt' would make the XML invalid. Fixes golang/go#17158 Change-Id: Ib3b5376094edc957ed15adf511bd1050ea13d27e Reviewed-on: https://go-review.googlesource.com/29297Reviewed-by: Nigel Tao <nigeltao@golang.org>
-
- 21 Oct, 2016 2 commits
-
-
Brad Fitzpatrick authored
Per RFC 7540, section 5.1 discussing the "idle" state: "Receiving any frame other than HEADERS or PRIORITY on a stream in this state MUST be treated as a connection error (Section 5.4.1) of type PROTOCOL_ERROR."x Updates golang/go#16046 Change-Id: Ie0696059e76a092e483aea5ee017d9729339d309 Reviewed-on: https://go-review.googlesource.com/31736 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Brad Fitzpatrick authored
Introduced by golang.org/cl/31447. grpc-go does concurrent Read/Close calls to the Request.Body. Since that was supported previously, continue to support it, and add a test. Updates grpc/grpc-go#938 Change-Id: I8a5cf6b28c5eca346ea46c4129021172e489f71d Reviewed-on: https://go-review.googlesource.com/31636 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 20 Oct, 2016 2 commits
-
-
Mikio Hara authored
The encoded data is just for debugging at kernel side and has remained in normal code path until now, oops. Change-Id: I3581bf73a6e6c9ec4b6228a670b6d8338f13ee14 Reviewed-on: https://go-review.googlesource.com/31535 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
The encoded data is just for debugging at kernel side and has remained in normal code path until now, oops. Change-Id: I28003ae211eb63d717d7e20f39ee0f39201892a5 Reviewed-on: https://go-review.googlesource.com/31534 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 19 Oct, 2016 1 commit
-
-
Brad Fitzpatrick authored
name old time/op new time/op delta ServerPosts-4 192µs ± 1% 164µs ± 1% -14.16% (p=0.000 n=17+19) name old alloc/op new alloc/op delta ServerPosts-4 69.8kB ± 0% 2.8kB ± 0% -95.95% (p=0.000 n=18+18) name old allocs/op new allocs/op delta ServerPosts-4 42.0 ± 0% 40.0 ± 0% -4.76% (p=0.000 n=20+20) This is a redo of git rev e7da8eda (golang.org/cl/20542) which had a race and was later reverted in golang.org/cl/21160. Updates golang/go#14960 Updates grpc/grpc-go#604 Change-Id: Ie216e45730dce4fc0c58f295bcbc669973145599 Reviewed-on: https://go-review.googlesource.com/31447 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 18 Oct, 2016 1 commit
-
-
Brad Fitzpatrick authored
Updates golang/go#17480 (fixes after vendor to std) Updates golang/go#17071 (a better fix than the original one) Change-Id: Ibb49d2cb825e28518e688b5c3e0952956a305050 Reviewed-on: https://go-review.googlesource.com/31326 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Chris Broadfoot <cbro@golang.org>
-
- 13 Oct, 2016 4 commits
-
-
Mikio Hara authored
Change-Id: I228f1405aac4ed058dafdfd5fc4cc609c56004fa Reviewed-on: https://go-review.googlesource.com/30897 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
The Read function of math/rand package doesn't exist on Go 1.5 or below. Change-Id: If837bbd0a862726be93e07b021701004ba0f0fad Reviewed-on: https://go-review.googlesource.com/30896 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
Change-Id: I95dfb05e5c958c2949059c4230c023968a442b50 Reviewed-on: https://go-review.googlesource.com/30895 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
Change-Id: Ifbc3848dcf1f7d43e3d781bcfe24e144ce028c32 Reviewed-on: https://go-review.googlesource.com/30894 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 12 Oct, 2016 1 commit
-
-
Artyom Pervukhin authored
Codec's Receive method calls io.ReadAll of the whole frame payload, which can be abused by user sending large payloads in order to exhaust server memory. Introduce limit on received payload size defined by Conn.MaxPayloadBytes. If payload size of the message read with Codec.Receive exceeds limit, ErrFrameTooLarge error is returned; the connection can still be recovered if required: the next call to Receive would at first discard leftovers of previous oversized message before processing the next one. Fixes golang/go#5082. Change-Id: Ib04acd7038474fee39a1719324daaec1c0c496b1 Reviewed-on: https://go-review.googlesource.com/23590Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 11 Oct, 2016 1 commit
-
-
Mikio Hara authored
From FreeBSD 11 both ip_len and ip_off fields of struct ip must be provided in network byte order. See IP(4) on FreeBSD. Change-Id: I091b551074767daf098cc1d6a256eddc4f55e304 Reviewed-on: https://go-review.googlesource.com/30736 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 07 Oct, 2016 5 commits
-
-
Radu Berinde authored
SetMaxEvent allocates storage for all events, which is very expensive if we want to set a high value; even with small values, the unnecessary allocation of the initial slice is measurable. We improve the performance by having a few events preallocated as part of the trace, and appending as necessary. We also co-locate the flags in event which makes it smaller (by a word). We also add a set of benchmarks; before and after amortized cost per-event is shown: name old time/op new time/op delta Trace_Default_2-32 1.19µs ± 1% 0.96µs ± 0% -18.94% Trace_Default_10-32 579ns ± 0% 635ns ± 1% +9.82% Trace_Default_100-32 463ns ± 1% 466ns ± 1% ~ Trace_Default_1000-32 451ns ± 1% 451ns ± 0% ~ Trace_Default_10000-32 451ns ± 2% 449ns ± 1% ~ Trace_10_2-32 1.41µs ± 1% 0.96µs ± 1% -31.74% Trace_10_10-32 623ns ± 1% 634ns ± 1% +1.73% Trace_10_100-32 469ns ± 1% 466ns ± 1% ~ Trace_10_1000-32 452ns ± 1% 453ns ± 2% ~ Trace_10_10000-32 451ns ± 1% 449ns ± 1% ~ Trace_100_2-32 2.78µs ± 2% 0.97µs ± 1% -65.28% Trace_100_10-32 912ns ± 1% 637ns ± 1% -30.23% Trace_100_100-32 479ns ± 1% 541ns ± 0% +12.77% Trace_100_1000-32 510ns ± 0% 541ns ± 1% +6.08% Trace_100_10000-32 514ns ± 1% 540ns ± 0% +5.14% Trace_1000_2-32 17.2µs ± 1% 1.0µs ± 1% -94.39% Trace_1000_10-32 3.90µs ± 1% 0.64µs ± 0% -83.68% Trace_1000_100-32 814ns ± 1% 542ns ± 0% -33.46% Trace_1000_1000-32 503ns ± 1% 581ns ± 0% +15.56% Trace_1000_10000-32 1.28µs ± 2% 1.03µs ± 1% -19.68% Change-Id: I5bbc12153a9f30dff821ef139583cb1c07a11069 Reviewed-on: https://go-review.googlesource.com/30615Reviewed-by: Ian Lance Taylor <iant@golang.org> Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Brad Fitzpatrick authored
This reverts commit If7c68bb1809fb92fa5d06cb6640be5e09e1f131f. Reason for revert: breaks the build for Go 1.6 or below due to use of Go 1.7+ only features. Original change's description: > trace: don't allocate all events upfront > > SetMaxEvent allocates storage for all events, which is very expensive > if we want to set a high value; even with small values, the > unnecessary allocation of the initial slice is measurable. > > We improve the performance by having a few events preallocated as part > of the trace, and appending as necessary. We also co-locate the flags > in event which makes it smaller (by a word). > > We also add a set of benchmarks; before and after amortized cost > per-event is shown: > > name old time/op new time/op delta > Trace/0-2-32 1.19µs ± 1% 0.96µs ± 0% -18.94% (p=0.008 n=5+5) > Trace/0-10-32 579ns ± 0% 635ns ± 1% +9.82% (p=0.008 n=5+5) > Trace/0-100-32 463ns ± 1% 466ns ± 1% ~ (p=0.190 n=5+5) > Trace/0-1000-32 451ns ± 1% 451ns ± 0% ~ (p=0.984 n=5+5) > Trace/0-10000-32 451ns ± 2% 449ns ± 1% ~ (p=0.492 n=5+5) > Trace/10-2-32 1.41µs ± 1% 0.96µs ± 1% -31.74% (p=0.008 n=5+5) > Trace/10-10-32 623ns ± 1% 634ns ± 1% +1.73% (p=0.008 n=5+5) > Trace/10-100-32 469ns ± 1% 466ns ± 1% ~ (p=0.357 n=5+5) > Trace/10-1000-32 452ns ± 1% 453ns ± 2% ~ (p=0.913 n=5+5) > Trace/10-10000-32 451ns ± 1% 449ns ± 1% ~ (p=0.175 n=5+5) > Trace/100-2-32 2.78µs ± 2% 0.97µs ± 1% -65.28% (p=0.008 n=5+5) > Trace/100-10-32 912ns ± 1% 637ns ± 1% -30.23% (p=0.008 n=5+5) > Trace/100-100-32 479ns ± 1% 541ns ± 0% +12.77% (p=0.008 n=5+5) > Trace/100-1000-32 510ns ± 0% 541ns ± 1% +6.08% (p=0.008 n=5+5) > Trace/100-10000-32 514ns ± 1% 540ns ± 0% +5.14% (p=0.008 n=5+5) > Trace/1000-2-32 17.2µs ± 1% 1.0µs ± 1% -94.39% (p=0.008 n=5+5) > Trace/1000-10-32 3.90µs ± 1% 0.64µs ± 0% -83.68% (p=0.008 n=5+5) > Trace/1000-100-32 814ns ± 1% 542ns ± 0% -33.46% (p=0.008 n=5+5) > Trace/1000-1000-32 503ns ± 1% 581ns ± 0% +15.56% (p=0.008 n=5+5) > Trace/1000-10000-32 1.28µs ± 2% 1.03µs ± 1% -19.68% (p=0.008 n=5+5) > > Change-Id: If7c68bb1809fb92fa5d06cb6640be5e09e1f131f > Reviewed-on: https://go-review.googlesource.com/30374 > Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> > TryBot-Result: Gobot Gobot <gobot@golang.org> > Reviewed-by: Ian Lance Taylor <iant@golang.org> > Change-Id: I7cf25464ae836489e0af4a59a4d534a5d25ee352 Reviewed-on: https://go-review.googlesource.com/30650Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
Mikio Hara authored
To match up with other packages that work with IP protocol stack. Change-Id: Idc3ee5b2399c4982dbd9114aac441f6d7452aeef Reviewed-on: https://go-review.googlesource.com/30576 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
To match up with other packages that work with IP protocol stack. Change-Id: I1f4eb76051964766113914c9698233022e73d5eb Reviewed-on: https://go-review.googlesource.com/30575 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
To match up with other packages that work with IP protocol stack. Change-Id: I2d20e4194617b05b6b46d6fba5df1f6c12ae2793 Reviewed-on: https://go-review.googlesource.com/30574 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 06 Oct, 2016 5 commits
-
-
Radu Berinde authored
SetMaxEvent allocates storage for all events, which is very expensive if we want to set a high value; even with small values, the unnecessary allocation of the initial slice is measurable. We improve the performance by having a few events preallocated as part of the trace, and appending as necessary. We also co-locate the flags in event which makes it smaller (by a word). We also add a set of benchmarks; before and after amortized cost per-event is shown: name old time/op new time/op delta Trace/0-2-32 1.19µs ± 1% 0.96µs ± 0% -18.94% (p=0.008 n=5+5) Trace/0-10-32 579ns ± 0% 635ns ± 1% +9.82% (p=0.008 n=5+5) Trace/0-100-32 463ns ± 1% 466ns ± 1% ~ (p=0.190 n=5+5) Trace/0-1000-32 451ns ± 1% 451ns ± 0% ~ (p=0.984 n=5+5) Trace/0-10000-32 451ns ± 2% 449ns ± 1% ~ (p=0.492 n=5+5) Trace/10-2-32 1.41µs ± 1% 0.96µs ± 1% -31.74% (p=0.008 n=5+5) Trace/10-10-32 623ns ± 1% 634ns ± 1% +1.73% (p=0.008 n=5+5) Trace/10-100-32 469ns ± 1% 466ns ± 1% ~ (p=0.357 n=5+5) Trace/10-1000-32 452ns ± 1% 453ns ± 2% ~ (p=0.913 n=5+5) Trace/10-10000-32 451ns ± 1% 449ns ± 1% ~ (p=0.175 n=5+5) Trace/100-2-32 2.78µs ± 2% 0.97µs ± 1% -65.28% (p=0.008 n=5+5) Trace/100-10-32 912ns ± 1% 637ns ± 1% -30.23% (p=0.008 n=5+5) Trace/100-100-32 479ns ± 1% 541ns ± 0% +12.77% (p=0.008 n=5+5) Trace/100-1000-32 510ns ± 0% 541ns ± 1% +6.08% (p=0.008 n=5+5) Trace/100-10000-32 514ns ± 1% 540ns ± 0% +5.14% (p=0.008 n=5+5) Trace/1000-2-32 17.2µs ± 1% 1.0µs ± 1% -94.39% (p=0.008 n=5+5) Trace/1000-10-32 3.90µs ± 1% 0.64µs ± 0% -83.68% (p=0.008 n=5+5) Trace/1000-100-32 814ns ± 1% 542ns ± 0% -33.46% (p=0.008 n=5+5) Trace/1000-1000-32 503ns ± 1% 581ns ± 0% +15.56% (p=0.008 n=5+5) Trace/1000-10000-32 1.28µs ± 2% 1.03µs ± 1% -19.68% (p=0.008 n=5+5) Change-Id: If7c68bb1809fb92fa5d06cb6640be5e09e1f131f Reviewed-on: https://go-review.googlesource.com/30374 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
The size of sockaddr_storage is fixed for interoperability on each platform. There is no need to depend on changable cgo-generated offset values. Change-Id: I54b775b2a8c86d969a6da0398a335075f0cbe3df Reviewed-on: https://go-review.googlesource.com/30178 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
The size of sockaddr_storage is fixed for interoperability on each platform. There is no need to depend on changable cgo-generated offset values. Change-Id: I7469fe330d49867bbdbdfae128834140244925ec Reviewed-on: https://go-review.googlesource.com/30177 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
This change adds support for Solaris. To read and write IPv6 ancillary data using ControlMessage, ipv6 pacakge requires https://go-review.googlesource.com/30171/ Note: Unlike other platforms, Solaris seems to have a few restrictions on ICMP property access via raw IP sockets. At least applications are prohibited from using IPV6_CHECKSUM option for ICMP transport. Fixes golang/go#17324. Change-Id: Ie014665d94ae6e4955c95d3eea88db90332e20bd Reviewed-on: https://go-review.googlesource.com/30176 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Mikio Hara authored
This change adds support for Solaris. To read and write IPv4 ancillary data using ControlMessage, ipv4 pacakge requires https://go-review.googlesource.com/30171/ Note: Unlike other platforms, Solaris seems to have a few restrictions on ICMP property access via raw IP sockets. At least applications are prohibited from using IP_RECVTTL option for ICMP transport. Fixes golang/go#17323. Change-Id: Icb6dfa3c8eced28d14693ddfea4601301999d735 Reviewed-on: https://go-review.googlesource.com/30175 Run-TryBot: Mikio Hara <mikioh.mikioh@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 03 Oct, 2016 4 commits
-
-
Mikio Hara authored
Change-Id: I8f05f473bb78336dd1ba788cfa09fc02797eb8dd Reviewed-on: https://go-review.googlesource.com/30174Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
Mikio Hara authored
Change-Id: I6b58c698527a1ebcb34fd1e08834bb5d7f33f49a Reviewed-on: https://go-review.googlesource.com/30173Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
Brad Fitzpatrick authored
Change-Id: I3fa5b27a4846807e8ed1265d696929037b77861b Reviewed-on: https://go-review.googlesource.com/30160Reviewed-by: Ian Lance Taylor <iant@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Cezar Sa Espinola authored
This change adds a Dialer field to websocket.Config struct. If this value is set the Dialer will be used. If it's nil, DialConfig will create an empty Dialer that will maintain the original behavior. Because before Go 1.3 there was no crypto/tls.DialWithDialer function, the Dialer will be ignored when opening TLS connections in these versions. Fixes golang/go#9198. Change-Id: If8b5c3c47019a3d367c436e3e60eb54bf0276184 Reviewed-on: https://go-review.googlesource.com/12191Reviewed-by: Russ Cox <rsc@golang.org>
-
- 01 Oct, 2016 3 commits
-
-
Ivan Babrou authored
Change-Id: I69d713341b878a2343bb85fb2de2ef49441fd16d Reviewed-on: https://go-review.googlesource.com/30098 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
Sam Whited authored
s/customise/customize/ s/authorisation/authorization/ Change-Id: I23afdca1b773ef9572794555dfb768c9ded90ab8 Reviewed-on: https://go-review.googlesource.com/30159Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
Brad Fitzpatrick authored
Tests in net/http: TestNoSniffExpectRequestBody_h2 Updates golang/go#16002 Change-Id: Ib5255c14f0a8fdafd36077b86442dff213815567 Reviewed-on: https://go-review.googlesource.com/30150 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 30 Sep, 2016 2 commits
-
-
Brad Fitzpatrick authored
Fix a regression from Go 1.5 to Go 1.6: when we introduced automatic HTTP/2 support in Go 1.6, we never handled Server.ReadTimeout. If a user set ReadTimeout, the net/http package would set the read deadline on the connection during the TLS handshake, but then the http2 package would never disarm it, killing the likely-still-in-use connection after the timeout period. This CL changes it to disarm the timeout after the first request headers, similar to net/http.Server. Unlike net/http.Server, we don't re-arm it on each idle period, because the definition of idle is more complicated with HTTP/2. No tests here for now. Tests will be in the go repo once all the knobs are in place and this is re-bundled into std, testing both http1 and http2. Updates golang/go#16450 (minimal fix for now) Updates golang/go#14204 (considering a new http1+http2 IdleTimeout knob) Change-Id: Iaa1570c118efda7dc0a65ba84cd77885699ec8fc Reviewed-on: https://go-review.googlesource.com/30077Reviewed-by: Ian Lance Taylor <iant@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Brad Fitzpatrick authored
Tests will be in the go repo's net/http package when this package is re-bundled into std. Updates golang/go#16808 (fixes after bundle into std) Change-Id: Iad31dc120bc008b1e9679bf7b2b988aac9c893c8 Reviewed-on: https://go-review.googlesource.com/30075 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 29 Sep, 2016 3 commits
-
-
Brad Fitzpatrick authored
https://golang.org/cl/29965 adding ClientConn.Ping support introduced a build failure on Go versions before 1.7. Fixes golang/go#17286 Change-Id: Ibfb565e7d823a436e58dc833973d7bdb41b7de5a Reviewed-on: https://go-review.googlesource.com/30071 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>
-
Olivier Poitrey authored
This new method sends a PING frame with random payload to the peer and wait for a PING ack with the same payload. In order to support cancellation and deadling, the Ping method takes a context as argument. Fixes golang/go#15475 Change-Id: I340133a67717af89556837cc531a885d116eba59 Reviewed-on: https://go-review.googlesource.com/29965Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
ayanamist authored
The existing implementation has a hardcoded "https" scheme for all request, since it allows http scheme in the request, it should use the scheme in the request url. Fixes golang/go#17257 Change-Id: Ibd9528df0328d7630ee94a006db694645625cdc9 Reviewed-on: https://go-review.googlesource.com/29975 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-